Nancy,

It really depends.

If it's a CreateObject() to some external object or even a reference to an already existing object, there isn't a requirement to explicitly .null. it. When the object finishes destructing that reference to the other object will be removed and the other object's reference counter will decrement.

If it's a reference to one of it's own contained objects it'll have to be .null.ed out so the object can destruct.

Either way, I think the best design is to explicitly set object ref properties to .null.

>That is not correct, as far as my experience goes.
>
>>I think if you put the object reference into a form's user-defined property, say THISFORM.oRef, you do not need an explicit release (THSIFORM.oRef=.NULL.),