I presume that Marcin is who started this, so this response is actually directed to Marcin. . .

It seems that if ANY reference anywhere at all might exist to any object, then that object will NOT be released from memory.
I base this SOLELY on the statement at top of page 72 of the VFP 5.0 Developer's Guide which states:
" However, because a reference to an object belonging to frmInvoice still exists, the object is NOT RELEASED FROM MEMORY UNTIL txtCustName is released with the following command:
RELEASE txtCustName "
Note that on the prior page txtCustName was setup as a reference to the object frmInvoice [ who would have guessed that these lines had anything to do with the next page, but that's the way MS has chosen to 'document' FoxPro, so that's what we get].

In the absence of any other relevant information, this is the best I can offer.

Good luck

>>I've just installed 5.0 and unfortunately faced a problem I can't cope with. Some forms are not possible to be released after any control was dragged form them. It doesn't happen always, but in 90% cases. All the forms are linked with a variable and all the controls being dragged are text boxes in a grid (manual dragging started with double-click). The variable (object) is destroyed but the form still exist and the only way to close it is to quit FoxPro.
>>
>>Can anybody help??
>Usually this is because a variable holds a reference to an object.
>
>Foxpro is supposed to release objects when the reference count is zero. But it doesn't seem to do it right every time.
>
>It is a very good idea for you to set all object pointers you create to .NULL. when you exit from a form because of that problem.
>
>
>When you say "the variable is destroyed" can you show me the code?
>How do you know the object is destroyed?
>
>Can you describe what your program is meant to do?
>And how the Drag and Drop achieves this?