>>>I am experiencing some extremely frustrating problems in VFP 3.0b. Randomly, forms that I have created within an application will not close. I have traced the code numerous times and the form is released (using RELEASE THISFORM), however, it remains on the screen and the application just stops handling the rest of the events. What makes the problem so frustrating is that I can cancel out of the unclosed forms, open the project, rebuild the .app, not touching any code whatsoever, and the form works fine. Each of the forms is an .SCX file based on my custom form classes, run using DO FORM .
>>>
>>>If anyone knows any cure or has an suggestions for either of these problems PLEASE let me know. TIA.
>>
>>Hello Jon,
>>
>>I'm using Vfp 5.0a here and I'm also facing this problem. What is worse is that it really seems to be randomic (I have never seen such a problem before).
>>Repeating exactly the same steps sometimes it happens sometimes not, and it makes no difference here building again the project as you've mentioned. The only difference is that here I have only seen it happening with forms instantiated with CREATEOBJECT and not with DO FORM.
>>
>>I know that array properties not set to .F. and external references to the Form object (or to one of its controls) not released before closing the Form cause the same problem (the Form doesn't close). BTW, it would be a great debug improvement in those situations to have a way of knowing what exactly is obstructing the form's closing process.
>>
>>What makes me very surprised is to be only now hearing for the first time about this problem. Are we the only chosen ones?
>>
>>Renato
>
>You can easily get into troubles using some innatural code like:
>oMyobjectc=Thisform.cmbCombo1
>oMyobject.value="qq"
>because now, you should (sometimes) firstly release oMyobject.

Sometimes I use what you call innatural code, specially if I need to deal many times with an object with a long hierarchy. It's easier to use a variable oMyobject, than issuing many times: Thisform.Pageframe1.page3.container7.cmbCombo1

But they are ALWAYS declared local variables.

Anyway that doesn't explain why the problem sometimes happens sometimes not...