I'm currently working my way through ASP.NET Unleashed. In the database samples the author closes the SqlConnection object, but never sets any of the objects (SqlConnection, SqlCommand) to Nothing. This was a recommended procedure in classic ASP. Is this no longer necessary?<BR><BR>If it's STILL recommended, what would be the proper syntax to accomplish this?Never hurts to explicitly set objects to nothing, but realize that setting them to nothing will not automatically get rid of them. The garbage collector (GC) does all of this for you. Once the variable goes out of scope (the page finishes being served from the Web server) the object will go out of scope and get cleaned up by the GC.<BR><BR>In any case, to set it to Nothing explicitly, do:<BR><BR>objConn = Nothing<BR><BR>Notice that you don't use the Set keyword. This keyword (along with Let) were removed in VB.NET (since default properties were also removed. See An Overview of Changes from VB 6 to VB.NET<BR>http://www.4guysfromrolla.com/webtech/053001-1.shtml<BR><BR>Happy Programming!.