Software

Ask something
Discussion Locked

Access: Not enough free memory to update

0 helpful
7 replies

by pchw

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

All of a sudden we have 3 users who get the following error message in Access 97 when trying to open a report: There is not enough free memory to update the display. Close unneeded programs.
They have been using this data base for a long time on their systems (NT4.0, 128mb ram). When they open forms, tables, etc., it runs fine. Looked at Technet Q142931 article, but doesn't help and doesn't quite apply. Any suggestions would be welcome. The database was working fine before, and no changes. Other people can access the database just fine.

7 replies

by gbworld

The answer really depends on how you have the database set up and what you are doing. The best way to use Access is to set up "shadow" databases for the users that link to the main database. This way, no errant databases affect the client.

Firstthing to look at is the database size and what the users are doing with the database. If it is large and they are opening across network, this can cause memory problems.

Next, look at the system. Make sure you have the latest patches to office 97 (service release).

My suggestion, if possible, is to move to SQL Server and use Access (local to client) as a shell for the SQL Server database by creating a linked database for the client.

One other thing to look at is whether these users have added any programs of their own, esp. TSRs. The most prominent is Screen saver programs that are made by people not familiar with the intricasies of screen savers; however, this is not the only culprit. Any program can have a memory leak, and TSRsare a particular problem.

Also, chekc for viruses. They often start eating memory due to the fact that virus authors are not concerned with damage. If you do not have virus protection, this is a good shot.

The problem tells me that there is a memory leak somewhere or the user has a lot of programs open. Memory leak is more probable.

Gregory A. Beamer
MCP: +I, SE, SD, DBA

by pchw

I finally found the answer, and I'm not going to give myself points, but I thought you might be interested in the answer, so I am posting it. It had to do with the printer. Once we set it a different printer as the default, it worked just fine. It appears the other printer had only 4 mb of memory (old printer) and it wasn't enough to preview the reports, even though it could preview everything else.

This discussion is closed to new replies.