David Emerson
davide at dalyn.co.nz
Tue Dec 2 18:09:28 CST 2003
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