>>>>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 .
>>
>>>
>>>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?
>>
>>
>>I hope we're not the only ones! Hopefully someone out there has some kind of solution or work-around. I initially thought it might be that I'm using the Cob Editor Extensions. Are you by any chance using that? Just a thought... Other than that, I've tried doing DISPLAY MEMO TO to see if any reference variables to the form were out there, but as of yet, haven't found anything. I had to demo the application that I'm having these problems with and, of course, the problem showed up in full force! I re-built the .EXE about four or five times and restarted VFP about the same amount of times, and finally got the stubborn thing to work. Boy, was I sweating. I'm sorry to hear that this problem exists in 5.0a, too. I was hoping I could at least blame it on the fact that I'm using 3.0b.
>
>Hi!
>
>It really looks like there are some object references that are still pointing to your object. For this reason, objects remain in memory, but you can usus\ally not talk to them anymore. In VFP3, a construction like this often leads to GPFs too. If that might be the case, then I can give you more advise how to deal with that...

Hi Markus,

Advises are always welcome.

So the point is: how can I know if my forms aren't (sometimes) releasing themselves because of external references? If so, how can we detect which is this reference?