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:
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.