Hi Christof,
It's too bad if VFP will appear to release the form if a control doesn't release, it sure makes diagnosis harder. On this form, I got rid of all containers, pageframes, etc., just kept a few standard framework textboxes and it still had a problem.

I love VFP but it does have some quirks. I've used "WAIT '' TIMEOUT .25" in methods before to fix problem behavior ( Didn't help here though). I even had a problem once, can't remember what it was now, that was only fixed by calling DISPLAY MEMORY NOCONSOLE in a particular place in the code! I had some flakey behavior that nothing could fix. I noticed that stopping execution and checking memory made everything OK and after trying WAIT to no avail, added the memory display and voila! It was healed!

It's particularly interesting that a very simple subsequent form, two combo boxes and two command buttons, called after the release of the form in question, controls its subsequent behavior.

Thanks again for all your help.

Gary


>Hi Gary,
>
>>I've put wait windows and sometimes set step on in Load, Init, Release, QueryUnload, Destroy and Unload and no matter how the form is closed, everything fires as expected.
>
>Wait Window is one of the commands that could alter the behavior. Anyway, most likely it's not the form that is causing a dangling reference - if there is any - but one of the contained controls. In this case you would see the form's Destroy event fire, but one contained control would not fire the Destroy event. Destroy happens outside in, therefore the form's Destroy event just marks the beginning of the series.