Freeing dynamically allocated memory (RESOLVED)

[divined]

Hello everybody

When I`m unloading dynamically allocated objetcs in memory I use the statements :

rsTexnikos.Close
connbio_tech.Close

where rsTexnikos is an ADODB.Recordset object and connbio_tech is an ADODB.Connection object. Do I need to do something else to successfully deallocate the memory? In some source code I was looking at the programmer used :

rsTexnikos = Nothing

Is this necessary or just a precaution against untimely use of a reference?

thx, in advance

George Papadopoulos

[Hack]

From MSDN:

Nothing

The Nothing keyword is used to disassociate an object variable from an actual object. Use the Set statement to assign Nothing to an object variable. For example:

Set MyObject = Nothing

Several object variables can refer to the same actual object. When Nothing is assigned to an object variable, that variable no longer refers to an actual object. When several object variables refer to the same object, memory and system resources associated with the object to which the variables refer are released only after all of them have been set to Nothing, either explicitly using Set, or implicitly after the last object variable set to Nothing goes out of scope.

[divined]

So, setting a reference to Nothing has effect only when there exist two or more references to an object. But, it doesn`t hurt having it one way or another.

[penagate]

It has effect when there is only one reference as well. Usually VB will destroy object references and generally clean up itself. But, as you say, it doesn't hurt to use it.

[Hack]

Usually VB will destroy object references and generally clean up itself.

Unfortunately, you can't trust this to always occur so setting an object to Nothing is more than advisable. IMO - it should be something you get in the habit of doing as second nature.