(VFP 8)
I have a queryunload event. When the form's name is reassigned to a character string:
myForm="ABC"
the test, TYPE('myForm'), returns a "C"
However, when the queryunload requests "myForm.release", the test returns the reference as an object. Even if I delay the test for a few seconds.

Is myForm.Release explicit?:)

I got to look at some VFP 6 code - maybe I have changed (or not followed:) my cwn coding standards.

Is your VFP 8 sensitive to "energy" saver sleepy drives. It seems VFP 8 has issues with a drive waiting wake-up.

>Terry,
>Anything that was an object remains an object until it is re-assigned explicitly to some other type OR RELEASEd.
>It can even be NULL in value but still be typed as an object.
>
>cheers
>
>
>>After responding - I was testing some work and this issue again re-appeared.
>>
>>Regarding forms and TYPE, the quuestion may be: How long will the form be considered an object after a release or queryinload?
>>
>>A micro-second - a few seconds - a minute ...?
>>
>>Even though I had X-Clicked and closed a form (maybe I did not explicictly do a release -), TYPE and VARTYPE both indicated the closed form was still an Object.
>>
>>My work around for to assign the form name a string (myForm="ABC"), to assure a character type. It worked. A few months back I think an explicit release of the form (in queryunload) worked.
>>
>>Maybe I need to explicitly release the form in the queryunload event. SThe struggle continues!
>>
>>
>>
>>
>>>Hello Terry.
>>>
>>>There was the thread from this message #879301. I think the issue was with vartype when the type was vetted the data had to be checked for null. It failed for me in my particular application.
>>>
>>>I looked at the thread. Interesting < s >. As I said, I have not experienced this problem. But now I will keep my eyes open and be on the lookout for it. I'll report back here if and when and happens to me < s >.