Discussion Locked

Microsoft Access 2000 "Out of Memory"

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

One of my company's owners programs various databases in Access 2000. She uses the VB editor in Access to create the code neccesary to perform the programming tasks. The problem is now she recieves an error "our of memory" while working in Access.She has to keep restarting Access to keep working. The PC is a P4 running Win98 SE with 1024 ram.

I looked into Microsoft's Knowledge base and found article 223235 that offered no solution.

Is there any way to fix this error and what might be causing it? I could use some insight here.

11 replies

by sgt_shultz

without a little more to go on, here is my knee-jerk response:
does it do it in safe mode?
does it do it with a fresh database?
can you pin it down to a certain operation in access?
are any other applications misbehaving?
what is showing in Close Program? anything you don't recognise in there?
do you have current virus defs and have you scanned all file types?
hope this helps some...

by planet1

Everything on the IT checklist with the PC, the condition of Windows, the condition of Access, and the security (antivirus) level are good here. That was the first place I went before trying to debug the Access database or Access itself.

by ann777

The last paragraph (-- specifically the last line --) of 223235 offers the resolution:

"The problem is based on a combination of the project size, the number of code windows that you have opened in the Visual Basic Editor, and the availability of system resources. After you have exceeded the system resources, however, you can no longer open the Visual Basic Editor in this project. Therefore, you must move all of the objects to a new database project."

There's also 217353 and 209940 --
Make sure Access 2000 has the latest Service Release installed as well

by highlander718

Is the file/application server by any chance a Novell one ? I know on those ones (as it happened to me with the same error) the tables(databases) are not closed properly when you close the application. Once the system reaches a specific number of "virtually open" databases it will give you this error message. Now there is a setting that you can modify (sorry, don't remember which one) on the server so that you can have more open databases but, but I don't think you want to do that as you might get into some bigger trouble.
I found this info on the Novell site or book at back then, not in the Mcrsft knowledge base. Do a search there, it might help..

by joe

I recommend 384MB for Win98.
More than 511MB can cause problems.

by planet1

The problem existed when the PC had 384 meg. I went from 128 to 256 to 384, and now am at 1024 meg. I think there is more than likely a memory leak in the database or in Access itself dealing with the VB editor.

by alpha48

When Access is loaded it only contains the default ability to work with 9000 records. "Somewhere" in the hot key reg. it can be increased to 15-20000 records. [I no longer have my print out from the ms site] This stopped several problems I was having. [Maybe starting here will help]

This discussion is closed to new replies.