Set the rs variable to nothing when finishing using it

[PEB]

I don't know is there any effect when i'm finishing to use a recordset from VB
and after
rs.close

i set rs to:

set rs=nothing

Pls explain me what is the effect of set rs=nothing

Is there any economy of memory, or something simillar??

I've tought that rs.close and then mydb.close are enough to close and free the memry for those objects...

Thank you

PEB

[NeoPa]

Every object variable is a link to an object (or it's set to Nothing).
This is particularly important to understand for temporary objects.
When an object var is set to nothing then it will be 'closed' automatically. This is handled by the compiler as differen objects have different meanings for 'Close'.
It is therefore not necessary to close the object explicitly.
However, whan a variable loses scope (a local variable in a procedure, for instance, when the procedure is 'Exit'ed), it is automatically set to nothing intrinsically.
The important thing about Temp objects is that they will remain in existense, only while at least one object variable refers to them. Once the last is set to Nothing, the object disappears.
It's also important to bear in mind, that there are code structures (With TempObj...End With is one that comes to mind) which will keep a link to the object similar to an object variable. In this case the temporary object would also remain until this usage or reference has been released.

[PEB]

Ok. Thanks NeoPa for this good explication.. In my case i've uset the recordset variable only in functions...

So when the functions finish their work the recordset object varibles that have been used desappear... So in my case there isn't any problem...

In those functions everytime i've used mys.close and mydb.close coz I've setted the database using set mydb=currentDb()

Maybe it's the time to say that if mydb is setted using Workspace and Database a command like mydb.close can close the current database directly...

So i don't need to correct my function writing Set rs= nothing

Thank you NeoPa
:)

[NeoPa]

I never use a separate variable for CurrentDB - CurrentDB is there, available all the time.
Also CurrentDB won't close with a call like

Call CurrentDB.Close()

[jasonphos]

I never use a separate variable for CurrentDB - CurrentDB is there, available all the time.
Also CurrentDB won't close with a call like

Call CurrentDB.Close()

Your suggestion is good from a pure coding standpoint, but when you consider performance, it may not work.

I tested this back in Access 97, and CurrentDB() calls are slow. I can't remember how slow, but I want to say at least 100 or 200ms. Maybe they've been sped up in latter Access versons? In any case, people should look out for this when using CurrentDB. Other than that, CurrentDB is great.

Jason

[NeoPa]

Interesting point Jason.
Would I take that to mean that assigning a db Variable to point to CurrentDB and using that variable in the following code would be a more efficient approach?
Where possible, I always use the With ... construct, which probably saves me from similar type issues in my code.

[NeoPa]

FYI This thread was done in my first fortnight as a member here.
Seems like a lifetime ago :D