not enough free memory inrunning Access query

Topic

New Reply

I have created a simple query joining 3 tables together with a calculated field in Access 2007. Whenever I execute the query, I always receive the error message “There isn’t enough free memory to update the display. Close unneeded programs and try again”. I have 4GB of RAM running Windows7 and Access 2007 is the only program running with lots of free RAM. I am wondering if there is a solution to that.

Thanks

Reply | Quote

Replies

Hard to say without having detailed information about the design of the query. Could you attach a stripped down and zipped copy of the database?

Reply | Quote

I have created a simple query joining 3 tables together with a calculated field in Access 2007. Whenever I execute the query, I always receive the error message “There isn’t enough free memory to update the display. Close unneeded programs and try again”. I have 4GB of RAM running Windows7 and Access 2007 is the only program running with lots of free RAM. I am wondering if there is a solution to that.

Thanks

Access out of memory solution
Finally, Microsoft says that in some cases, this error message appears when you perform operations on large tables because the MaxLocks PerFile value in the Windows Registry is set too low. From the Registry Editor, expand HKEY_LOCAL_MACHINESOFTWAREMICROSOFTJET4.0Engines and click the Jet 4.0 folder. Double-click the MaxLocksPerFile entry in the Name column in the right pane, and when the Edit DWORD Value box appears, choose the Decimal radio button to change the Value Data box to a format that humans can understand. On our test system, the value was set at 15,000, so bump that number up to a larger value such as 50,000, click OK, and close the Registry Editor. You may need to experiment to find a setting that works, and it’s a good idea to jot down the original number in case you you need to revert to it to make Access 2003 run properly. Hopefully this may work with Access 2007.Good Luck

Reply | Quote

Increasing the Max Locks may work, however, you say you are joining three tables and there is a calculated field. If you remove the calculated field, does the query joining the tables work? One of two things may be happening. One – The calculated field has a null value or produces an error such as divide by zero that is interfering with the joins or Two – You managed to produce a cartesian product and are getting too many results.

My suggestion is to first try the queries without the calculated field to see if the joins work. If not, then try running the query by joining only two of the three tables to see where the issue is occurring.

What are the join types, Inner, Outer, or other? HTH

Reply | Quote