[AccessD] Setting objects to Nothing

Hi Jim,

<<<
Always a good idea to clean up after yourself.
>>>
Yes.

<<<
At least in the case of Access, you can't always 
count on it to do the job for you.  
>>>
Well, in fact setting ref to Nothing is only needed for the case of
cross-referenced object instances but to be 100% sure you didn't miss to
handle such a case use settings to Nothing everywhere - it does cost that
much, and it can save your hair...

--
Shamil


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Tuesday, February 16, 2010 6:57 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Setting objects to Nothing


  Always.  Also do this:


  On Error resume next

  If not rstMyRecordSet is nothing then
    rstMyRecordSet.Close
    Set rstMyRecordSet = Nothing
  End If

  Always a good idea to clean up after yourself.  At least in the case of
Access, you can't always count on it to do the job for you.  

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Tuesday, February 16, 2010 10:00 AM
To: AccessD at databaseadvisors.com
Subject: [AccessD] Setting objects to Nothing

When referencing a Reference object, do any of you bother with 

Set ref = Nothing

????

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

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4871 (20100216) __________

The message was checked by ESET NOD32 Antivirus.

http://www.esetnod32.ru


 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4871 (20100216) __________

The message was checked by ESET NOD32 Antivirus.

http://www.esetnod32.ru