>>>Mike-
>>>
>>>>I see no way to make the query continue if the user hits escape. To me the whole point is that the user is tired of waiting and wants to quit. If they hit escape by mistake, they'll have to learn to be more careful. You could put a window behind the progress bar, which advertises the escape key and warns of the consequences.
>>>
>>>FWIW, one can, if one allows Fox handle the escape, but I wouldn't even dream of suggesting that to Nadya.
>>
>>Care to demonstrate having the query continue after hitting escape?
>
>IIRC, all you have to do is SET ESCAPE ON, then when asked if you want to cancel, say no.

There would have to be no error handler in effect, so that's not good. But beyond that you get Cancel, Suspend, Ignore. Ignore seems to continue at the next line, without returning records, rather than continuing with the query.

>
>Updated: Also, IIRC, there can be quite a bit of lag time between the time the user presses escape and the app responds. I don't recall at all how it compares to using one's own SET ESCAPE routine.

There seems to be no difference in the time lag with one's own routine or without.