Erwin Craps
Erwin.Craps at ithelps.be
Tue Dec 2 18:53:26 CST 2003
Charlotte can be right on this, You should check other OS issues to. Virtual memory is independant of physical memory. Adding RAM will not necesarily solve your Virtual memory problem. This you can easely check with the task manager while you experiance the prob. It is Windows that manages the virual memory, it can be a memory leak, but it can be a wrong setting to. Check the page fiels size in Start>Control panel > System >advanced > performance settings > advanced (I'm translating from dutch so I could be mistaking in names, but you'll get the drift) Virtual memory > Change Look below to see how big the page file is. I have 512MB RAM to. My recommend size is 766MB and momentary admitted is 1534MB managed by windows. Posibly the size has been limited to a fixed size or by disk capacity or fragmentation. My Advice: Put al disks (one by one) to no paging file or as small as posible Reboot Defrag your disks one by one. Reboot (just to be sure) Set a fixed size of paging file on one or more (FYSICAL) disks (no point in spreading page file over patitions on same fysical disk) I would advice a paging file total size of 1534B and maximum 2500 (or something) in your case. Reboot. Pay attention that you still have plenty of space on your c disk (where windows is). The printer spooler will spool jobs to the windows system32\spool folder. If not enough space you could receive simular error. It is posible to change the location of the spool folder. You could consider (due to the nature of your printjobs) to change the location to another partition of your disk, that you would only use for this purpose. Defragmentating of this disk would be easier. Do a regular defrag. If I remember well the paging is limited in it's growth by the availability of large enough free blocks on the disk. Having no such large spaces could result in a lack of virtual memory. Thast why fixing a big enough size at forehand will guarantee you enough room to work with. Hope this helps. Erwin -----Oorspronkelijk bericht----- Van: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] Namens Charlotte Foust Verzonden: woensdag 3 december 2003 1:21 Aan: Access Developers discussion and problem solving Onderwerp: RE: [AccessD] Access keeping memory resources 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 _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com