Hi!
I know that. But when you have public variable, better to cleanup it, otherwise next Public statement will throw an error if such variable already exists in the memory. I usually do this for public variables.
>Hi Vlad,
>FWIW, you don't really need the two commands. Once you execute the object's Release method, any variable that was referencing that object is now set to .NULL..
>
>Regards.
>
>>Hi!
>>
>>Well, this is quite a complex question. Many programmers solve it by different ways. For example, create garbage collection programs. Or create special classes to track cross-references. Personally, I like the approach on the OOP and design level. Just create a method "Release" for your business object. SOe releasing of it will now require 2 commands:
>>
>>goBusiness.Release()
>>release goBusiness
>>
>
>*snip*
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.
