But it "is" cleaned up in the sense that testing the object variable against Nothing returns true. It's state is now the equivelant of the object variable had I issued the "Set ObjectInstance = Nothing" statement.
VB Code:
  1. CopyMemory mobjTest1, 0&, 4&
  2. CopyMemory mobjTest2, 0&, 4&
  3.  
  4. MsgBox mobjTest1 Is Nothing
  5. MsgBox mobjTest2 Is Nothing
Both display True.

I understand that VB will eventually handle this for you. I however, am very anal. If I open it, then I try to close it. If I create it, then I try to destroy it. Regardless of whether or not I "need" to.

Actually, I am quite suprised that a simple thank you to Wokawidget for inadvertantly feeding my anal retentiveness, has exploded in the manner that it has.

I don't believe that I have misunderstood what has been communicated here. If any of my posts have given the impression to the contrary, then I guess that I need to work more on my communication skills.