> IMO, always set to nothing, if you hit the problem where the ROT isn't
> cleared properly it's the devils own job finding where it's happening, far
> easier in the long run to get in the habit of removing the objects
yourself.

> Bill Berry wrote in message ...
> >I want a rule-of-thumb on whether every procedure that uses a local
> >recordset (or other DAO) object variable needs to have Set
> <objname>=Nothing
> >at the end.

> >I understand that there are many dark corners and details to this issue,
> but
> >I'mmainly concerned with the simple scenarios exemplified below:

> >I'm writing a function (that may be called hundreds of times per day)
that
> >uses a recordset object to look up some data. I'm just returning a string
> >value from the function, not any objectreferences. All variables in the
> >procedure are local-to-the-procedure in scope. If one of those variables
is
> >a recordset, will it automatically be "set to Nothing" when it goes out
of
> >scope (i.e. the procedure finishes) or do I have to manually do a
> >Set<variable>=Nothing ?.

> >I want to do the right thing to keep memory "clean and tidy", but I don't
> >want to have (lots of?!) Set <variable>=Nothing statements which are
> >functionally redundant.

> >Please help me with the straight scoop on this basic situation. TIA

> >Bill Berry