Tracy,

Hopefully the procedure will stop gracefully if the form stays active. And, as far as escape code, if you could just post the ON ESCAPE line (if that is what is used), if ON ESCAPE calls a function please post it. Also, show what tests are done during the loop to see if the escape key was hit.

Talk to ya Monday...

>The code in the procedure to trap for escape is the problem. There are actually almost 20 little procedures that are called from the menu and I would have to put it in everyone. The procedure is run under FPD26 AND VFP7 so I have to enclose everthing inside of #IF 'VISUAL' $ UPPER(VERSION())
>to make it safe to run under both versions which is why I really don't want to do too much coding to trap for the escape key. However, the rest of the app traps for escape and returns to the calling program so I would like the same function. It works in FPD26 because a screen is run instead of a form, but in VFP7 of course the form is open. The cancel button effectively cancels the form and I release all other objects that I created, but of course the procedure still keeps running. I'll test it with the cancel on the cancel button set to .f. and see if I can grab the escape coding and post it.
>Tracy
>