Hi Sergey,

I just tried something new with this. I tried calling the form from a test menu I created that has no other option. It worked fine in that case, so it's not just that it's being called from the menu. I call the same code to set all the SET commands whether I call the form directly or from within my app, so I'm not sure what the difference is. It's definately something that the app is doing, but I can't figure out what.

>Hi Barbara,
>
>Is it a modal form? Would it make a difference if you launch it from menu using a timer?
>
>>I've got a really strange problem. I've got a form that runs a long process within a loop. I want the user to be able to hit Escape to exit the loop. I've implemented this in the standard way:
>>

>>llXit = .F.
>>on escape llXit = .T.
>>set escape on
>>scan while not llXit
>>   ... Processing code here
>>   DOEVENTS
>>endif
>>

>>This works as expected if I just DO FORM.... from the Command Window. However, if I call it from the menu of my app, it either ignores the Escape key or hangs. The menu option is just a command that says DO FORM... just like I do from the command window. The form has a private datasession.
>>
>>I'm sure there's some difference in the environment between the two situations that's causing this difference in behavior, but I can't figure out what it is. Anyone have suggestions as to what I can check?