Cleaning Up Your Code

[SgtJarrow]

OK, code gurus.....

Simple question....Which is better to "clean up" your code at the end of a procedure and why:

Set rs = Nothing

or

rs.Close

Any other suggestions for "properly" closing down a procedure? Please remember to give helpful posts the stars they deserve!
This makes the post more visible to others in need!

Robert L. Johnson III, A+, Network+, MCP
Access Developer/Programmer
robert.l.johnson.iii@citigroup.com

 

[GKProgrammer]

Well I always add the code in my procedure to close recordset objects etc that are declared in the closing procedure but you have to remember that whether you implicitly add the code or not once you exit a procedure that declares Connection, Database, or Recordset objects, those objects are closed automatically. Regards,
gkprogrammer

 

[mp9]

Maybe it's becuase I'm paranoid (or at least you guys all think I am, ha ha) but I sometimes put both the

Set

and

Close

statements in.

Having said that, I would imagine

rs.Close

tp be sufficient. GKProgrammer makes a good point to put it in your Exit code, so that the closure still happens even if you "shortcut" to the Exit code via an error handler.

For an ADO recordset you could use its

State

property in your Exit code to only close the recordset if it's open, which is quite neat.

http://www22.brinkster.com/accessory/