Not Enough Memory To Update The Display

[chaddy]

I am using Athlon 1800XP, 256mb of ram, Windows 98 & Access 97 through a network and keep getting 'There Isn't Enough Free Memory To Update The Display. Close Unneeded Programs And Try Again' on a couple of machines.

I have looked at the microsoft website and there is an article about this but it says it only relates to access 2000.

Does anybody know what could be causing this.....?

 

[lamarw]

Hmm interesting. I believe your are running out of physical or virtual machine memory. This can happen when alot of coding is opening recordsets or databases but then they are not closed again. ie
Set db = CurrentDb
Set rs = db.OpenRecordset(...)
but then at the end of the procedure there is no corresponding:
Set db = Nothing
Set rs = Nothing
or
db.close
rs.close
Each opening of a database and a recordset consumes memory and if you do it enough you will run out. Does this help?

 

[chaddy]

I am opening a database and opening forms using
DoCmd.OpenForm
and to close
DoCmd.Close
and yes there is quite a lot of coding when opening the forms, clicking buttons on the form, etc....
Sorry for being thick, but if this is the problem how do I get round it.......

 

[willir]

chaddy

256 MB on an system running FAT16 and FAT32 (windows 9x andME) is usually plenty.

I am going to approach this from a hardware OS perspective first...

- Do you have other applicaiton open? Are any of them buggy -- ie, memory leaks? Hint: If a computer runs fine in the morning but tends to crashes in the afternoon suggests a memory leak, and dwindling resources. Hint: Close other applications and see if you still get the same error.

- Have you applied the SR2 for Office 97? It fixes some of the memory leaks (especially in Word).

- Have you deleted your TEMP file? And while you are at it, delete your temparary Internet files.

- Do you have more than 200 MB free on the hard drive(s)?

- Is your swap file / virtual memory file big enough and in the right location? Richt click on My PC, properties, performance. A typical installation of Windows - lets Windows control the swap file, and Windows will usually use the C: drive. If you have more than one drive, the C: drive is usually NOT the perferred location. And with 256 MB, a typical rule of thumb is to set the swap file to twice the size, i.e. 512 MB in your case.

With Access, it will run and retrieve an entire recordset even for the simplest query.

Using a "Select *" when you only need "Select CustomerID" can make a difference. I would focus on the combo boxes, and proably the current record event.

lamarw comment regarding open record sets is very valid. An open recordset could mean that the contents of a table or tables is left open serveral times on a form.

Get rid of, or restrict the use of graphics. I had one developer embed a beautiful picture in hist forms. Looked stunning with lots of oohhs and aahhs, but then one could say a lot of oohhs and aahhs while the form was loading. And user got errors regarding resources. When I convinced him to remove the graphics, the forms did not look as slick but now it worked.

While you are at it, simplify or get rid of the graphics on the screen saver and wallpaper. These pictures, especially in Win 9x environment is extremely wasteful. Pleasing to the eye - yes, but degrades performance and uses memory.

Richard