When you set a recordset to nothing, it is supposed to
close the recordset if nothing else is using it.
When you close a recordset, it closes the recordset even
if something else is using it.
If you sensibly only use the recordset once, in one place,
then it makes no difference if you close the recordset, or
set it to nothing, or let it go out of scope.
Apart from that, there are various arguments based on coding
style, which environment you are using (asp frequently has
different scope than Access VBA), and bugs in long gone
versions of Access.
(david)
"Dave" <(E-Mail Removed)> wrote in message
news

78DEC65-252E-4AF9-A7A7-(E-Mail Removed)...
> Hi,
> Can anyone explain the difference and benefit (if any) between using the
> close statement and the Nothing statement?
> For example, when I clean up at the end of a procedure:
>
> rst.Close
>
> OR
>
> set rst = Nothing
>
> Thanks
> Dave