[AccessD] Access keeping memory resources

Charlotte Foust cfoust at infostatsystems.com
Tue Dec 2 18:21:17 CST 2003


Usually, that means "leaky" code.  Are you explicitly destroying the
object variables?  Has the job actually printed or is it still being
spooled to/by the printer?  

Charlotte Foust

-----Original Message-----
From: David Emerson [mailto:davide at dalyn.co.nz] 
Sent: Tuesday, December 02, 2003 4:09 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Access keeping memory resources


Group,

WXP, AXP ade / SQL 2K BE

I have an accounts report which is printed off at the end of each 
month.  There are about 1800 customers and each account is 2 pages.  I
have 
set up my program so that it prints them in batches (groups of 600 
customers at a time - this results in a print job of about 50MB).  When
the 
first batch is finished a box appears asking if the first batch is to be

reprinted or the next one done.  The operator waits until the first
batch 
is completely printed before sending the next batch to the printer.

The problem is that Access doesn't free up the physical memory between 
batches with the result that a "virtual memory low" errors appear and
the 
print jobs stop ignominiously.

We found that running a single batch, closing Access, then opening it
again 
frees memory for the next batch.  However this is not an acceptable 
solution.  The computer has 500Mb memory at the moment and we are going
to 
increase this to 1GB, however this will only delay the evil day.

Does anyone know why Access doesn't free up the resources once it has 
finished with them, or how we can do it without closing Access between 
print jobs?

Regards

David Emerson
Dalyn Software Ltd
25 Cunliffe St, Churton Park
Wellington, New Zealand
Ph/Fax (877) 456-1205 

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


More information about the AccessD mailing list