[AccessD] Access keeping memory resources

Sorry I wasn't clearer.  I was actually referring to a command -

Dim cmd As adodb.Command

This was in a function that I hadn't set the cmd = nothing.

I had another function that used the same variable for several commands.  I 
have just set it to nothing at the end of the function rather than doing so 
at the end of each use. EG

     Set cmd = basGetCommand("sprptAccountPrintCustNo", adCmdStoredProc)
     cmd.Execute
     Set cmd = basGetCommand("sprptAccountPrintCustNames", adCmdStoredProc)
     cmd.Execute
     Set cmd = Nothing

David


At 3/12/2003, you wrote:

>David
>A recordset need to be closed AND set to nothing!!!
>
>Set rst = something
>Do_your_thing
>rst.close
>Set rst = nothing
>
>Set rst = something
>Do_your_thing
>rst.close
>Set rst = nothing
>
>
>
>
>-----Oorspronkelijk bericht-----
>Van: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] Namens David Emerson
>Verzonden: woensdag 3 december 2003 2:12
>Aan: Access Developers discussion and problem solving
>Onderwerp: RE: [AccessD] Access keeping memory resources
>
>Ah,  I did find a couple that were missed.  I will try that.
>
>As a side issue,  If a recordset variable is being used several times in
>a procedure, should it be set to Nothing between being set to a
>different record set, or is it ok just to set it to nothing at the end
>of the procedure?
>
>David
>
>At 2/12/2003, you wrote:
> >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
>
>_______________________________________________
>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