>>>>Hi Vladimir,
>>>> Sorry to be troublesome, but I could not get the keyboard shortcuts to work even naming my menu pad as a system menu pad name. Plus, I may not have been clear in my problem description. I am instantiating a standard menu in the form ( not a short cut menu ) containing standard keyboard short cut keys defined in the menu designer. The form has objects on it and is not acting as a "desktop". The menu's keyboard shortcuts will not fire. Is there a particular form property setting required for menu keyboard shortcuts to fire in a top level form? Any other thoughts?
>>>>
>>>>Thanks,
>>>>Bill
>>>
>>>It's just a guess: Private Data Session Form will restore all environment settings to default, probably, 'cleaning' shortcuts. Anyway the solution might be to 'declare' all necessary shortcuts firing appropriate code from Form.KeyPress event.
>>
>>Hi Edward,
>> Thanks for the reply. I thought about using the form.keypress event to fire the desired menu actions, but the event does not seem to "see" ALT+whatever keypresses even with form keypreview set to .T.. Seems to have something to do with the "ALT" part of the keypress or some interaction between the top level form and the menu or something. I do not yet have a lot of experience with top level forms, but what I have indicates they are somewhat finicky, especially with an instantiated menu. I will give this some more thought.
>>
>>Thanks,
>>Bill
>
>I didn't expect that KeyPress doesn't react on ALT-keys (at least, it does react for normal form). BTW, there is second parameter in KeyPress event "nShiftAltCtrl" which additionally indicates ALT key pressed.

Thanks Edward. I was testing on the nshiftAltCtrl parameter also. It was just that an Alt+whateverkey was not firing the keypress event. I figured the event would fire, then test nKeyCode and nShiftAltCtrl to determine key combination.

Bill