>No, I don't have any CLEAR KEYBOARD in my code. Thank you.
>
>>Just a SWAG........which could be WAY off........
>>
>>Does myProc have a CLEAR KEYBOARD, or anything that reads keystrokes so that the ESCAPE has already been processed by the time you hit the DOEVENTS????
>>
>>>I have a long process that goes between SCAN and ENDSCAN of a cursor. The process goes in a click() method of a button. I placed the following code in the procedure:
>>>
>>>

>>>set escape on
>>>lStop = .F.
>>>on escape lStop = .T.
>>>select MyCursor
>>>scan
>>>    DO MyProc()
>>>    doevents
>>>    if lStop
>>>       =messagebox("Cancel procedure",36,"Cancel?") = 7
>>>       exit
>>>    endif
>>>endscan
>>>

>>>
>>>But the =messagebox() never sees the action. What do you suggest?
>>>
>>>Thank you.

In general, the code you have should work. I don't like structures like EXIT and LOOP, so taking Naomi's advice I'd convert it to something like

set escape on
lStop = .F.
on escape lStop = ( messagebox("Cancel procedure",36,"Cancel?") = 7 )
select MyCursor
scan WHILE NOT lStop
    DO MyProc()
    doevents  && Should be optional
endscan

As for why it's not working, have you traced your code? Is it possible MyProc() does not exit (i.e. infinite loop)? Are there any rows in MyCursor (e.g. is it filtered so there are none)? Is the code somewhere in a subclassed ActiveX? In a case like this tracing/debugging should point out pretty quickly where the problem lies.