Not enough memory error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We are experiencing problems running an Access 97 mde on a Windows 2000 Advanced Server via Terminal Services. The server is also running MS Exchange Server 2000 and MS ISA server and has 1GB of physical RAM.

When using our application we are getting the error message below saying that it has run out of memory but there are no messages recorded in the Windows event viewer warning of low memory problems and also Task Manager says that the peak memory that has been used is 1.5GB out of a maximum 2.5GB. The error message is intermittant and there doesn't seem to be a way of being able to cause it to happen intentionally. We are also experiencing a problem where the Acesss runtime locks up and the TS session has to be terminated.

'The expression On Error you entered as the event property setting produced the following error: There isn't enough memory to perform this operation. Close unneeded programs and try the operation again'
 
My experience indicates you are running out of a specific type of memory, probably "System" memory. If my memory isn't too fuzzy (I'm sure it really is), it's either System or GDI memory you are having problems with. "System" memory available to your MS Access application is quite limited, and involves things such as handles and threads to open windows, etc. GDI memory relates to pens and other drawing objects Windows uses to draw your screen.

I received such an "out of memory" error during the building of a large application here at INVESCO. I was able to cause this by using the roller button on the mouse, where the numerous subforms I had open just couldn't seem to keep up, and there's the dreaded error. The solution is to lighten the object memory load. Specifically, a number of subforms would display only if a user chose a specific tab. Therefore, I only loaded the subform for the tab the user was on.

No more memory error for me. Stable my application is.

David Atkins, MCP
 
Does Access get allocated a certain amount of System memory or it is free to keep grabbing System memory until the server runs out? If it is the first case, then would upgrading to Access XP help? If it is the second, then could it be down to other applications on the server using up the System memory as we do not have this problem on other servers.

Thanks.
 
I apologize for the delay in responding. I've just now done a seach for follow-ups.

As I understand it, MS Access is provided with a certain amount of System memory, but I would not take this to the bank. I believe you are asking very appropriate and pointed questions, and without research, I am unable to answer them.

Speculating, it would seem reasonable to suspect that other applications are consuming resources that MS Access may otherwise have used.

I apologize for not being more helpful. When I encounter these memory issues (as I have more than a couple times in the past when trying to be over-ambitious), I simply begin to employ memory-lightening techniques.

I would welcome additional input from SME's.

David Atkins, MCP
 
Back
Top