>Thanks again Nick for your suggestions but I think the only way this menu effect will work is if it was native to VFP.
>
>I can turn the menu on and off with your onF10 program and if I add KEYBOARD "{F10}" PLAIN the menu will be "activated". Now that the menu has been activated pressing F10 will no longer turn the menu off. It seems that once the menu is being used any ON KEY LABEL definitions are temporarily cleared.

It actually takes one more keystroke on F10 to turn off the menu.

>
>I would also have to redefine the Esc key so that the menu would turn off if Escape was pressed but in the same way once the menu is in use the Esc key loses it's ON KEY definition.
>
>I would also have to put something in each menu selection to turn the menu off otherwise the menu is left on after a selection is made.
>
>Another problem is that when the menu is turned on the screen moves down to accomodate the space used by the menu. I don't want the screen moving. I would have to write code to reposition every form so that F10 (or Alt) could be pressed from anywhere in the program.

That's what I said from the beginning. But you probably can find the workaround a little different way by always having the "empty" menu bar and show necessary menu bars only when F10 is pressed (before KEYBOARD "{F10}" PLAIN ) Didn't test it though - just an idea.

>
>Even if the F10 thing could be made to work is there any way to do the same for the ALT key?

As I said, you are actually fighting the Windows way of doing things here (you know - that "One Microsoft Way" :), not the VFP.


>I think I am just asking too much. FPD has it but I just don't think what I want is feasible in VFP.
>
>Thanks for your help Nick.