[AccessD] Ac2013 running out of resources

[Jim Dettman]

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

 "Resources" can mean many things, not just memory.

  One thing I mean to mention was adding the line:

  dbEngine.Setoption dbMaxLocksPerFile, 100000

 and see if it flies.  Not sure how many records your dealing with (and it
sounds more like you have an actual resource leak), but running out of locks
is another common source of "out of resources".  This one though typically
manifests when you have very large recordsets.  Won't hurt to try it though
and it's easy to do.

 Another common resource that runs out is table ID's.  Internally Access
uses table IDs for tracking open table objects and has a limit that floats
around 2048.   That sounds like a lot, but a table ID is used whenever
something refers to a table (not only a table that's opened, but fields,
controls, etc), so it's easy to run out.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Bill Benson
Sent: Friday, June 05, 2015 10:46 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Ac2013 running out of resources

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.
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com