>>I have many forms in my app but only one menu I call mainmenu. Based on user access rights I disable/enable each menu item in the menu designer. What I would like to do is have a seperate menu for each form. I've played around with push & pop menu and some other menu commands, but I can't get it to work quite right. what is the best approach to accomplish this? Thanks for any suggestions!!
>>
>>john.
>
>Hi John,
>
>I do exactly what you're after. I have labeled my menus according to the level
>that they are show at. You can name yours anything. The key to how I'm doing
>this is that in my form template, I have a property called nMenuLevel. In
>the .Activate() event of that template I have the following;
>
>lcMenu = "Level" + ALLTRIM(STR(THISFORM.nMenuLevel))
>goApp.DoMenu(lcMenu)
>
>Anytime a particular form activates, it automatically runs the menu I want.
>
>Steve

That sounds too simple...and it works fine...that's how I like it, and Thanks for the great idea. I have run into a new situation now though. Most of my forms up until now have been modal, except for my "main" form, or the one that my users spend most of their time in. I've noticed that when a form is modal, the menu items are disabled, which makes complete since, but now that I need to change most of these forms to modeless, what do I do about READ EVENTS. How would I best initiate event processing for these new modeless forms so that they just don't zoom by when instanciating them. I have one READ EVENTS in my main.prg after calling my main form, but thats all I've used in the past because other than my main form, the rest were modal. If you have time to respond to this garbled message, I sure would like to hear how you would handle this situation. Thanks again for your help with the menus!

John.