>>>Without getting too complicated with the telling, we have an SCX that can have an @Say screen popup over it using a hot key. We have code on almost all of our objects to close the form if the right-click of the mouse is done. On @Say screens, we have ON KEY LABEL handling the right-click of the mouse to do the same. What is happening is that if the @Say is over the form, when we right-click, the @Say screen closes, but then immediately the form does also. We have tried a number of things like CLEAR TYPEAHEAD and DO WHILE INKEY(0,'M') > 0...enddo, but to no avail. Anyone have any ideas? We are almost to the point of putting up an invisible form under the @Say screen, but above the SCX and letting both of those close, keeping the SCX open. But I really don't like those sort of solutions.
>>
>>I don't think you can debug this deep enough to find out what's going on.
>>
>>Can't you host the @Say screen in a form? Just createobject() a form, Show Window (oForm.name), set that form's font to something monospace and then do your 2.6 magic. When you exit the Read, kill this form and you're done; the code in the popup will (my guess, fingers crossed) consume its evil powers on this host form.
>>
>>Worth a try, eh?
>>
>>(if this is what you're already doing, then go for that transparent kamikaze form - you can create it just when you want to show this popup, and remove it when done, if it's still there)
>
>This worked. I changed the call to the @SAY screen PRG to a call to a form that took the command to run the PRG as a parameter. Little bit of tweaking, but now the form takes the errant RightClick code that is still floating around instead of the original calling form. Works great. Thanks!

Nice to know it still works. I did something like that once during a lunch break at a conference, on someone's laptop, where we got the whole fpd2.6 app to run inside a form. It was in VFP 6 or 7.