Hi again Sergey,
CLEAR MACROS seems to work but it doesn't prevent the ALT key from activating the menu. Hmmmm, now if I could only trap for the ALT KEY in the form. Do I HAVE to release the menu while the form is running in order to trap for ALT key combinations in the form's keypress?
>Tracy,
>
>I use '*' to disable keys.
PUSH KEY CLEAR
>ON KEY LABEL F4 *
>ON KEY LABEL F5 *
>ON KEY LABEL F6 *
>ON KEY LABEL F8 *
>ON KEY LABEL F9 *
>ON KEY LABEL ALT+S *
>ON KEY LABEL ALT+F5 *
>ON KEY LABEL ALT+F6 *
>...
>
>>In the evironment before a form is instantiated, the following keys are set:
>>
><snip>>
>>In the program that calls a form, I issue:
>>
>>
>>PUSH KEY CLEAR
>>ON KEY LABEL F4 ON KEY
>>ON KEY LABEL F5 ON KEY
>>ON KEY LABEL F6 ON KEY
>>ON KEY LABEL F8 ON KEY
>>ON KEY LABEL F9 ON KEY
>>ON KEY LABEL ALT+S ON KEY
>>ON KEY LABEL ALT+F5 ON KEY
>>ON KEY LABEL ALT+F6 ON KEY
>>
>>DO FORM ag_scrn NAME oag_scrn LINKED
>>IF TYPE('oag_scrn') = "O" .and. !ISNULL(oag_scrn)
>> oag_scrn.release()
>>ENDIF
>>RELEASE oag_scrn
>>
>>POP KEY
>>
>>The form's keypreview is set to .t. and in the form's keypress event I check for some of the function keys as so:
>>
><snip>>
>>However, stepping through it, the function keys are still sending chr(13) while the form is running. Also, the ALT key combinations still active the menu automatically. What am I missing to stop this so I can trap for the keys and process appropriately...
>>
>>TIA!
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"