>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?
If you haven't tried it already, you could use the coverage profile to see if there's any difference in what's getting run in the two circumstances.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up