I noticed the issue when a project of mine issued a "Remove" object. It seemed to take a while for the "object" to be "visually" removed. Setting visible to f seemed "inefficient", but it [at least] did what was needed.!:-)

>Thanks! That did seem to resolve the problem, but it does not seem intuitive that a release does not destroy the form, but setting visible to false does allow the form to destroy itself.
>
>>Maybe:
>>frmMyFormClass.visible=.f.
>>
>>>Nope. That did not make a difference.
>>>Is it not posible to release a class defined form that is instantiated as a variable?
>>>
>>>>Maybe:
>>>>
>>>>procedure frmMyFormClassCloseButton.Click
>>>>frmMyFormClass.release
>>>>endproc
>>>>
>>>>procedure frmMyFormClass.release
>>>>frmMyFormClass.queryunload
>>>>endproc
>>>>
>>>>>Why won't this form release?
>>>>>
>>>>>Have a form class in a vcx with a close button with 'release thisform' or 'thisform.release()' in the click method.
>>>>>
>>>>>In another form have a button with this in the click method:
>>>>>

>>>>>local oForm
>>>>>oForm=newobject('frmMyFormClass','myClassLibrary.vcx')
>>>>>oForm.show(1)
>>>>>

>>>>>
>>>>>Clicking on the close button on the myFormClass form does not release the form! I have to click on the 'X' in the titlebar to close the form. Why is that? If this is unstandard code, how would I lauch a form that exists only as a class?