>>>>>Why does the PUSH KEY CLEAR and POP KEY not work? I thought that's what they were for? To clear the last ON KEY LABEL commands in the stack and then pull them back.
>>>>
>>>>I don't know why they don't work. I don't use OKL unless I purposefully need an intercommand interrupt so I don't run into using PUSH KEY and POP KEY at all. For key shortcuts I usually use a menu defined but not displayed and assign the keys to the menu bars. Then I can use set skip to turn the individual keys on or off as needed and the menu is only available when VFP is in a user input mode automatically so there is no need to turn the keys on and off as code blocks execute, the menu isn't available while code is running.
>>>
>>>Well, even using ON KEY or ON KEY LABEL F7 or ON KEY LABEL F7 * or ON KEY LABEL F7 STORE .F. TO VarForNothing, the F7 hotkey still interrupts the processing. We must have something else going on. Is there a way to find out where in the processing that the key is being allowed to activate? The processing is all reasonably new code that does not contain @SAY stuff, so there are no hidden READ/DO EVENTS or anything like that that I'm aware of.
>>
>>A popup with F7 as the key?
>
>Hmmm... Maybe a form with a button that has a SET STEP ON in the CLICK?

Whatever is being called by F7, put a Set Step On in that, and then see how did it get called. Also check what does popup() return at that point.