>Christian,
>
>>This was my first guess too. I tried this (and a lot more), but there seems to be no reference hanging at all.
>
>Well none that we can see or control. *s* Sometimes internal references dangle and we can't clear them other to avoid the code construct that causes them.
>
>>Besides, if you have a reference and you remove the object, the reference itself is being destroyed as well.
>
>I still prefer to explicitly clear references, just a defensive coding habit.
>
>>Also what is happening is, that the same code that is called from the button
>

>THISFORM.DoProcess

>>works fine, and when using the key F10

>ON KEY LABEL F10 _SCREEN.ACTIVEFORM.DoProcess()

>>the problem occurs. There must be a connection with the ON KEY, the code itself must be good.
>
>It's not good to assume that _screen.ActiveForm is going to be your form at the instant the user hits the key. When forms are concerned there isn't a need for global OKLs, you can use KeyPreview = .t. and the form KeyPress() method to trap the F10 key press while the form has focus. You might see if this helps get rid of the internal reference that is holding up the form.

That was great, it did the job! Thanks a lot.