Frank,

>I found that VFP7 is more strict concerning open object references.

I am glad to hear that...at least I know I am not crazy!

>I found that when going from VFP6 to 7 in all of theese cases it
>was always a dangling oR that VFP6 simply threw away while 7 couldn't
>(or did not want to).

OK...maybe instead of worrying about the children of this form I need to see how I am instantiating it and make sure I am not leaving anything hanging around...

>I had theese specially when doing things with OLE-Controls / OCX's and
>still was in a method or an event of that control while I wanted to
>close the form. Normally everything was fine, but when I stress-tested
>my apps and produced errors within the control's methods. There
>sometimes was no way release the control that caused the error and thus
>no way to release the form
>So I strictly took those away from this kind of controls
>by separating them via timers.

...timer code snipped...

Sounds interesting...I hopefully will not have to go as far as this type of scheme, at least I hope not. All my other forms behave fine, and the problem form is even OK except for certain scenarios (which I am proceeding to isolate to try to debug).

>An event of an OCX/OLE-Control now always sets a timer and immediately
>returns to the control. a few ms later the timer fires once and calls
>a method in a true VFP-object

I have had issues with OCX controls, but usually focus and graphics-related...I will keep this in mind as I try to troubleshoot this issue more...thanks for the response!

JoeK