Gary,

>(1) Although, I have renamed my GL project 'amenus' classlib to 'aGLMenus', the main menu class is still 'mainmenu', so it appears the origial 'mainmenu' class is seen first and that is the one instantiated. Do I have to also rename all my menu class names to be unique between projects to have the right ones picked up?

That's probably true...

>(2) When the menus are swapped in and out from a method originating on the application class like the test above (forgetting the wrong one is instantiating) they work, however, when I call a method I've added to myAppClass.ShowAnyMenu() from a menubar click it Instantiates OK (forgetting the wrong one is instantiating) and then immediately I see each menubar and Pad destroy event fire and the whole menu is removed. It's almost as If because the menu and menubar that made the call to remove and replace itself, after the call is complete, the destroy methods run against the new menu. In other words, calling a app method to swap a menu from a menu pad click, I can't get it to stay around after it's built.

This *is* odd behavior...unfortunately, I'm not sure why you're experiencing this!

Regards,