[AccessD] Ac2013 running out of resources

Bill Benson bensonforums at gmail.com
Fri Jun 5 09:46:05 CDT 2015


Update:

As of the last time running this, I got up to 72 reports. I watched my Mem
Usage in my Task Manager slowly creep from 3.75 GB up to 5.15. And I do
mean slowly creep. As soon as it hit 5.15, I got the out of resources
error. When I clicked End, there was no change in resource consumption. And
that fits with the sypmtom that as soon as I run out of resources, nothing
can be edited in the database.

I have got to find a way to stop this process from consuming resources.
However, I note that even if I run only one style report (with about 30
outputted reports), and let the process end there, the mem usage does not
decrease in order to enable me to begin the next batch. I feel therefore
that I am screwed, if I want to keep outputting to PDF.

When I kill Access, I have 3.67 GB showing.

When I load Access (but do not start his database) I have 3.71 GB showing.

When I start this database I have 3.72 GB showing.

When I enable macros, I have 3.75 GB showing.

When I run some code that populates a list of reports to be run into some
controls on my Form, I have 3.76GB showing.

As I run the code that generates the PDF output reports, that creeps up to
5.15, as I said.

This leads me to conclude that Ac2013 is willing to use WELL UNDER 2 GB of
ram before declaring itself to be out of resources.

I have an 8GB machine, running under Windows 7.


More information about the AccessD mailing list