CODEWITHSUNDEEP
ms-accessram
Dule Marin
Dule Marin

Reputation: 3

MS Access: There isn't enough memory to perform this operation (Reports)

There are some of the posts with the same subject but the behavior I have with my MS Access application (with SQL Server database) is different than others.

On my PC (Win10 Pro, 8GB DDR4 2GB free), and the majority of clients 'PCs, it works perfectly fine. But on two of the clients' machines, reports couldn't be open even in Design mode (all reports, and just the reports - forms, queries are fine). All of the reports are very simple, with up to one subreport.

So, when the client wants to open a report he received msg box: "There isn't enough memory to perform this operation. Close unneeded programs and try the operation again."

Both of them have enough RAM. The first one has 12GB DDR3 (7,5 GB free), and another one has 8GB DDR3 (3,5 GB free). Both are using Windows 10 Pro and Office 365.

I tried to:

  1. Increase Paging File (Virtual Memory)
  2. Setting "Graphics performance preference" to "Power saving" for MS Access
  3. Disc Clean-Up
  4. Reinstall MS Office

Upvotes: 0

Views: 1636

Answers (3)

Jerzy Gebler
Jerzy Gebler

Reputation: 969

For the past year, I had exactly the same problem in an environment with Microsoft Office 365 64-bit version (2016 and newer). The application contains 17 reports. On 80 computers all reports opened without a problem, on 10 computers one report did not open at all, only reported the error ActiveX component can't create object, but during debugging I found the source error: There isn't enough memory to perform this operation.

I reinstalled Office, compared the registers, everything seemed to be correct, but I kept getting the exact same error. I deleted the report and imported it from the backup file, decompiled the application (option /decompile) and still the same error.

What was the solution to the problem?

I created a new blank report, set it to exactly the same DataSource, the same grouping and sorting, and copied all the controls to it, section by section from the non-working report. The report works correctly and opens without any problems on all computers.

It looks like it wasn't a Microsoft Office installation issue, but an internal error in the Microsoft Access file.

Upvotes: 1

Aidan Caelli
Aidan Caelli

Reputation: 16

In my application, an AutoExec macro is responsible for setting application options and initiating the login form. Usually, upon login (considering it uses a SQL Server backend, linking tables/pass-through queries), I would test if the reports were operational after the fact.

For some reason, the problem is consistently repeatable on versions 16501.20196, but doesn't manifest on 16327.XXXXX.

I found a workaround for this issue, here's how you can check if it will work for you: Hold the shift key while opening the file and select a report of your choice to open (you could even create a blank report solely for this testing purpose). Open and close this report prior to logging in or running any code.

Following this procedure, upon login, the reports should function as expected.

As a temporary solution, I've incorporated the open/close report in print preview as the initial action in my AutoExec macro. This seems to alleviate the issue for now, at least until Microsoft addresses the root cause.

Please consider this a workaround rather than a definitive solution.

Upvotes: 0

Sergio Bucci
Sergio Bucci

Reputation: 1

Did it happen after the Office 365 update 2305? It happened also to us and with Microsoft we are trying to sort out the reason (that in our case is connected to the update 2305 build 16501.20196). Also here there is a new post about https://techcommunity.microsoft.com/t5/access-blog/access-releases-14-issue-fixes-in-version-2305-released-june-1st/bc-p/3841797

If yes, contact Microsoft through the feedback function inside Access (so maybe with more cases they are able to find what it's in common).

Upvotes: 0

Related Questions