According to the Help file (for SET ESCAPE):

"If the user presses ESC during command or program execution, processing completes at the current program line, and an alert appears with the following three options:"

(them being Cancel/Suspend/Ignore). Are you sure it is interrupting the SELECT? Or stopping just after the SELECT line?

I haven;t been able to get the program to respond to the ESCAPE until after the SELECT is done, and by then it doesn;t matter.

Anyway, per another response by Ed R., a DOEVENTS seems to be critical to intercepting the ESC. By only hitting the DOEVENTS every 2 seconds or so, I seem to be getting okay performance out of the SELECT.

If anyone is interested in what I did, I can post it. It's mostly just a rehash of a couple of other suggestions found on UT.

jd