BUG ? Not enough free memory to update display !
Vladimir Pjevic
Under Win95 and Access 7 when I open form and after that change the height
of the Windows taskbar I got the message :
There isn't enough free memory to update the display...
PC is 133Mhz 486 with 32Mb RAM with 2MB Video Card.
Is this realy a memory problem or small bug ?
Kevin Mickey
On 12 Oct 1996 00:16:42 GMT, "Vladimir Pjevic" <pje...@opennet.org>
wrote:
I was just going to post almost the identical thing when I caught your
article. I am also using Win95 Access 7 and get the same memory
notice. This has happens on two computers which I have.
I have tried the following things:
removing any other running programs from ths startup group
using CTRL-ALT-DEL to bring up a window and kill all apps other
than Explorer and Systray
fooling with the virtual memory settings
reducing the display to lower and lower settings (down to 16)
rebooting the computer several times.
One computer is a Dell XPS 200n Pentiurm Pro with 32 Mb of RAM, over
1 gig free on the hard drive, and a 4 Mb video card. The other is a
generic 486 50 Mhz with 32 Mb of RAM, over 500 Mb free on the hard
drive, and a 2 Mb video card.
On both systems, the system resources are always reported to be
between 88 and 93 percent free. The system monitor reports 36-37 MB
of memory allocated on both systems with 9.7 Mb available. I know
that Access requires 12 Mb RAM to work, but on these systems I thought
that Windows would automatically reconfigure or increase the size of
the swap file dynamically to provide this to the program.
I am sorry for the long post, but I REALLY need to get this program
working and any help beyond these things would be helpful.
Thanks in advance.
Kevin Mickey
KJMi...@worldnet.att.net
Bradley Gouldson
In my experience this usually happens after you have run out of resources,
sometimes
because your database has incomplete transactions.. but I thought Win95 was
supposed to stop most resource problems.. It definately isn't a memory
problem..
check your available resources before you run your db, while it is running,
and after
you try resizing the taskbar. If the resources disapear when running your
db (more than
what could be considereed normal) look at your db. Has it got any code that
could be
stealing resources? Hope some of this helps..
--
Regards,
Bradley Gouldson
Software Developer
-------------------------------------------------
CORE Option (C)reating
Level 2, 517 Flinders Lane (O)rganisational
Melbourne 3000 (R)esource
Australia (E)fficency
Telephone: +61 3 96142211 Fax: +61 3 96142288
Vladimir Pjevic <pje...@opennet.org> wrote in article
<01bbb483$e88eaac0$LocalHost@pjevicserver>...
Mike Neal
What nerve! Bill's Stuff has no bugs, only "Non-Issues." Have this
blasphemer flogged and thrown in the dungeon! Had you suggested the
presence of a 'Major Bug', you would have surely been beheaded...
:)
Jack Mullins
Vladimir Pjevic <pje...@opennet.org> wrote in article
<01bbb483$e88eaac0$LocalHost@pjevicserver>...
> Under Win95 and Access 7 when I open form and after that change the
height
> of the Windows taskbar I got the message :
>
> There isn't enough free memory to update the display...
>
> PC is 133Mhz 486 with 32Mb RAM with 2MB Video Card.
>
> Is this realy a memory problem or small bug ?
>
>
The following is an excerpt from a MS Knowlege Base article. It is the
only info that I could find that references the error msg that you are
getting. However, I had a problem a few weeks ago with this error when I
opened any report in preview mode. Since I had no problems with any other
Win95 apps I reasoned that it had to be a problem with Access. I run on a
P5-100 with 32 meg and plenty of free disk space in the virtual memory
area. I removed all other running apps but still got the error. I finally
broke down and call Access Support. The problem turned out to be a bad
Lexmark printer driver. I was told that bad display drivers can cause the
same problem. The tech said that he had seen this problem fairly often,
but I could find no reference to it in the MS support databases or in the
news groups. I know it doesn't sound like the printer driver should cause
this error, but in my case updating the driver solved the problem. If
nothing in the KB article applies to your problem, try changing to the
standard print or VGA display drivers. Good luck.
Jack
*******************************************************************
PRA: "Not Enough Memory to Update Display" Error Message
Article ID: Q142931
Revision Date: 20-SEP-1996
The information in this article applies to:
- Microsoft Access version 7.0
SYMPTOMS
Novice: Requires knowledge of the user interface on single-user computers.
When you run Microsoft Access for Windows 95 version 7.0, you may receive
the following error message:
Not enough memory to update the display.
This error can occur at different times, for example:
- When you open a database with a startup form (as specified in the
Startup options on the Tools menu).
- When you use a main form with a subform control that has its
NavigationButtons property set to Yes.
- When you change Windows system settings (such as fonts, printer drivers,
colors, and so on) while a main form with a subform that contains
navigation buttons is open.
RESOLUTION
The resolution is dependent on the action you were performing at the time
you received the error message:
- If you receive the error message while opening a database with a startup
form, you can use an AutoExec macro to open the form instead of the
Startup options on the Tools menu. To do so, follow these steps:
1. On the Tools menu, click Startup.
2. In the Startup box, under Display Form, select the (none) option.
3. Click OK to close the Startup box.
4. In the Database window, click the Macros tab, and then click New.
5. Create the following new macro:
Macro Name Action
----------------------
AutoExec OpenForm
AutoExec Actions
----------------------
OpenForm
Form Name: <form name>
6. Close and save the AutoExec macro.
7. Close and reopen your database. The AutoExec macro should open
your startup form automatically when you open the database.
- If you receive the error message while using a subform with the
NavigationButtons property set to Yes, you can turn off the
NavigationButtons property and add custom navigation buttons using
the Command Button Wizard. If your subform is displayed in Datasheet
view, you also need to change the DefaultView property to Continuous
Forms. To do so, follow these steps:
1. Open your main form in Design view and delete the subform control.
(Note that this deletes only the control, not the actual subform
object which is listed under Forms in the Database window.)
2. Switch to the Database window, click the Forms tab, and then click
New.
3. In the New Form box, select the AutoForm: Tabular Wizard, select the
table or query where the object's data comes from, and then click OK.
4. View the new form in Design view, and then set the following form
properties:
DefaultView: Continuous Forms
NavigationButtons: No
5. Use the Command Button Wizard to add four new command buttons to the
form footer section. In the Command Button Wizard, under Actions,
select one of the following actions for each command button:
Go to First Record
Go to Last Record
Go to Next Record
Go to Previous Record
6. Close and save the new form as NewSubformTest.
7. Switch to your main form in Design view, and then drag the
NewSubformTest form from the Database window to the main form and
drop it in the former location of the original subform.
8. Customize the subform control as appropriate; for example, set the
LinkChildFields and LinkMasterFields properties.
9. Save your main form and switch the form to Form view. The subform
control should simulate a form Datasheet view.
- If you receive the error message after you change Windows system
settings while a mainform/subform that contains navigation buttons is
open, you should quit Microsoft Access and restart the application. The
best workaround for this situation is to quit Microsoft Access before
you make any system changes.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Access for
Windows 95 version 7.0. We are researching this problem and will post new
information here in the Microsoft Knowledge Base as it becomes available.
Additional reference words: 7.00
------------------------------------------------------------------------
KBCategory: kbenv kberrmsg
KBSubcategory: EvnGpf
Mike Deam
"Jack Mullins" <jac...@airmail.net> wrote:
>Vladimir Pjevic <pje...@opennet.org> wrote in article
><01bbb483$e88eaac0$LocalHost@pjevicserver>...
>> Under Win95 and Access 7 when I open form and after that change the
>height
>> of the Windows taskbar I got the message :
>>
>> There isn't enough free memory to update the display...
>>
>> PC is 133Mhz 486 with 32Mb RAM with 2MB Video Card.
>>
>> Is this realy a memory problem or small bug ?
>>
>>
> Snip ....
>The problem turned out to be a bad
>Lexmark printer driver. I was told that bad display drivers can cause the
>same problem. The tech said that he had seen this problem fairly often,
>but I could find no reference to it in the MS support databases or in the
>news groups. I know it doesn't sound like the printer driver should cause
>this error, but in my case updating the driver solved the problem. If
>nothing in the KB article applies to your problem, try changing to the
>standard print or VGA display drivers. Good luck.
>Jack
I get this fairly often. Well enough anyway. Word, Excel, Quattro Pro,
Access and Powerpoint have all been offenders at one time or another.
So it would seem not to be an application problem!
From what I can make out the printer driver also has quite a bit to do
with the display fonts in Windows. If you don't install a printer then
you get some default fonts. But from what I can work out the fonts,
printer driver and whats displayed is all tied up somewhere together
and the problem we are experiencing is nothing to do with the hardware
we throw at it. It's most likely to be some form of memory leak in the
printer driver IMHO.
My common thread I have with you Jack, is a Lexmark Printer a 4029 PS
Model 20 (042) my Father gets the same thing on a standard 4019E what
level print driver did you install?
Cheers
Mike Deam
mike...@c032.aone.net.au
Jack Mullins
Mike Deam <mike...@c032.aone.net.au> wrote in article
<542bks$1...@news.mel.aone.net.au>...
>
> I get this fairly often. Well enough anyway. Word, Excel, Quattro Pro,
> Access and Powerpoint have all been offenders at one time or another.
> So it would seem not to be an application problem!
>
> From what I can make out the printer driver also has quite a bit to do
> with the display fonts in Windows. If you don't install a printer then
> you get some default fonts. But from what I can work out the fonts,
> printer driver and whats displayed is all tied up somewhere together
> and the problem we are experiencing is nothing to do with the hardware
> we throw at it. It's most likely to be some form of memory leak in the
> printer driver IMHO.
>
> My common thread I have with you Jack, is a Lexmark Printer a 4029 PS
> Model 20 (042) my Father gets the same thing on a standard 4019E what
> level print driver did you install?
>
> Cheers
>
> Mike Deam
> mike...@c032.aone.net.au
>
>
Mike,
You are right in your interpretation of the interaction between fonts,
print drivers, and display drivers. In the world of WYSIWYG the display
driver has to have information from the other two in order to write the
screen. In my case I don't know what version of Lexmark's print driver
caused the problem, but 4.10 of the Optra R PS driver has solved the
problem, however the "memory leak" also occurred in PCL5 mode(now version
96.6.10). So, some common file in the driver release was probably the
culprit.
The MS Access tech that I spoke with was one of their first level type
guys, so he wasn't really up on the nuts and bolts of the problem. I guess
that I was lucky that he was aware that print and display drivers could
cause the "not enough free memory" error message. "Free Memory is the old
under 1 meg region and I thought that Win95 protected mode wasn't too
concerned about it but I guess bad drivers can still bring it to it's
knees.
here is Lexmark's driver page, if you haven't already been there:
http://www.lexmark.com/inotes/drivers/driversus.html
I don't know if drivers for your printer share anything in common with
Optra series, but it's possible. Also, in my case, I only had the problem
running Access and it was not an occasional error. Anyway, in your case,
it still sounds like it would be worthwhile to update the printer driver.
Later....
Jack
Charles E. Robinson
I get this same problem if I use QuickRes to change my resolution. I
have an STB Lightspeed 128 video card, I am the only person in the
office with one, and I am the only person who has this problem. I was
using QuickRes to switch between 1024 x 768 and 800 x 600 while I was
developing some Access forms. I was trying to make sure they would
display properly at a resolution and color depth different from what I
was using, but QuickRes or my video driver wasn't happy with that.
Charles
crob...@mindspring.com
Teo Stresen-Reuter
We have an STB driver too, but I don't know which one ;-)