Has anybody experienced getting out of memory errors in Access 2000. Usually it starts when trying to write some VBA code and then gets progressively worse until it happens continueously. I have reloaded Access several times and it will work for a while. I installed another 128 meg of RAM and that did nothing since the error reoccurred immediately. Any suggestions??
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Access 2000 out of memory error
- Thread starter cmmrfrds
- Start date
I suppose you have a lot of FREE disk space.<br>
Is your database really large like over 50Meg?<br>
Also check to see what your Page file size is?<br>
Are you in NT workstation or '9x?<br>
<p> DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br>
Is your database really large like over 50Meg?<br>
Also check to see what your Page file size is?<br>
Are you in NT workstation or '9x?<br>
<p> DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br>
- Thread starter
- #3
Doug.<br>
I have 15 giga bytes free out of 20.<br>
app is 4 meg linked to database of 1.2 meg.<br>
Windows 98.<br>
??? not sure what "page file" is ??<br>
There are about 85 Forms and 40 functions (separate module) in VBA and some VBA behind most Forms.
I have 15 giga bytes free out of 20.<br>
app is 4 meg linked to database of 1.2 meg.<br>
Windows 98.<br>
??? not sure what "page file" is ??<br>
There are about 85 Forms and 40 functions (separate module) in VBA and some VBA behind most Forms.
- Thread starter
- #4
I got the solution and the diagnosis of the "out of memory" problem.<br>
<br>
I called Microsoft Technical Support. It is a known problem, but in my case there was no articles in the knowledge base. Initially, tech support thought the problem was with pictures that were defined as gif(s). There is a memory leak when Access 2000 converts the .gif to wmf for internal use, but I was not using .gif(s).They had me do a Control G and check how many Forms and Modules were open with VBA code. All of my forms and modules were open, so we closed them all --- 85 Forms and one module with 40 Functions. Closed down Access and even rebooted, when I opened Access again all the Forms were still open. I had converted the mdb from Access 97 originally. The SOLUTION was to create a new mdb in Access 2000 and import all the objects. I can now close the Forms and Module and they will stay closed, so no more memory problem. By the way, in NT the problem didn't show up because it seems to allocate the resources better, I am using Windows 98 on my PC.<br>
<br>
The solution led to additional problems with libraries but that is now solved.
<br>
I called Microsoft Technical Support. It is a known problem, but in my case there was no articles in the knowledge base. Initially, tech support thought the problem was with pictures that were defined as gif(s). There is a memory leak when Access 2000 converts the .gif to wmf for internal use, but I was not using .gif(s).They had me do a Control G and check how many Forms and Modules were open with VBA code. All of my forms and modules were open, so we closed them all --- 85 Forms and one module with 40 Functions. Closed down Access and even rebooted, when I opened Access again all the Forms were still open. I had converted the mdb from Access 97 originally. The SOLUTION was to create a new mdb in Access 2000 and import all the objects. I can now close the Forms and Module and they will stay closed, so no more memory problem. By the way, in NT the problem didn't show up because it seems to allocate the resources better, I am using Windows 98 on my PC.<br>
<br>
The solution led to additional problems with libraries but that is now solved.
- Status
Similar threads
- Locked
- Question