Mace,

I have used other user interfaces for my menus including the one suggested. The main problem with that approach is security control. I am trying to get a handle building a large application with seperate menus invoked for each module so I can use the MMortals built in security. I haven't been successful in ending one menu and beginning another. I can successfully stop the current menu, but as soon a my new menu is finished building, it acts like it has no object reference and excutes the destroy events until there is no menu displayed at all. Here is my new method I've added to my subclass of cApplication :

PROCEDURE ShowAnyMenu
LPARAMETERS tcMenuClass
     IF PCOUNT() < 1
	tcMenuClass = "MainMenu"
     ENDIF
     THIS.ReleaseMenu()
     THIS.REMOVEOBJECT('oMenu')
     THIS.ADDOBJECT('omenu',THIS.oICSFactory.GetClassName(tcMenuClass), "goApp.oMenu")
ENDPROC

>Gary,
>
>Have you thought about using top-level forms for your applets? You could define one form for each module app and define an applet specific menu to run in the top level form.
>
>Mace
>
>>I have a common MM project that acts as the manager of my accounting app of several module apps (GL,AP,etc). I will need to display a different main menu as each module is selected to be the current application the user wants to work in. I have studied the framework goApp.DO() method and saw where it is calling showmenu(). I could add a parameter, to the call so that if a parameter is passed, It could be an abstractfactory key to load a different menu after removing the current one. I thought I would ask, however, if there isn't a more "approved" method for changing the entire menu. I think it should be in here somewhere but I can't find any mention of how to do it.
>>
>>Does anyone have a solution they are using that works well?
>>
>>Gary Pike.