Hi Rick,

>I don't think so - if you have left over references in other areas of
>your code that object will stick around.

Nope. Actually there are two commands in VFP that don't take care about the internal reference counter, one is RELEASE THIS, the other THIS.RemoveObject().

>Doing RELEASE THIS is also not safe, because you're telling the object to
>release itself before state is cleaned up.

Somehow I don't grasp this. If RELEASE THIS is in my Release method and I call loObject.Release I tell the object to release itself, since I don't need it anymore. Why shouldn't that be safe?

>I firmly believe that you should never release your object internally,
>at least not through the language. Rather I belive in having Release
>methods that make sure that when the object goes away all hanging
>refs get cleaned up properly.

That's exactly what Mark and I are talking about.

Christof