I ment to mention, we make the custom.cui the main menu in all profiles for a given user.
So the enterprise menu changes between profiles, but not the main menu.
James Maeding
|>Bill,
|>We do what you are describing with no problem in 2006.
|>Each person has their own custom.cui, which starts out as a copy of the acad.cui (or actually the acmap.cui since we use
|>LDT)
|>That custom.cui gets stored in their profile folder.
|>Their custom .cui has various partial menus loaded, the partials are standard menus that users do not edit.
|>
|>So each user logs in, starts acad to their profile, and works away.
|>User A is not affected by user B and so on since the main menu is different for each user.
|>
|>The CUI system is a pain, but has just enough freedom built in (barely enough) to do what we used to be able to do.
|>
|>We use the enterprise menu as a method of loading partials that you want in one profile, but not another.
|>You would always want the same main menu for all profiles, but use different enterprise menus to load different
|>combinations of partial menus for each profile.
|>
|>BillZ <>
|>|>>>>jbryant4 wrote:
|>|>No, just load the .mnu as Partial CUI Files.....Basically the same as before. <<<
|>|>
|>|>Okay, maybe I just don't understand it yet and we are heavily customized here.
|>|>
|>|>The way we do it now, is that everyone works off their own .MNS and profile. The reason being is that we had so much trouble when shared machines between nightshift and dayshift. Seemed like the changes that were made on one machine affected the .MNS/interface of the other user on that same machine.
|>|>
|>|>What I did to solve the problem, was, to check each username at startup and make sure that the profile that belonged to them was set current and saved at the begining of the session. That way, any changes that were made to their interface (toolbars) were made to their own custom .mns. And if anyone crashed out during a session, the profile could be restored and it would be current because the profile had been saved regularly.
|>|>
|>|>Right now we all read off the same startup files and share the network files that run our custom apps.
|>|>Can I still do something like we do now?
|>|>
|>|>So what am I looking at for 2007.
|>|>
|>|>
|>|>We completely ignored 2006 because of all the problems that we see posted here about going to CUI, but we really don't care to get too far behind on releases either.
|>|>
|>|>TIA
|>|>
|>|>Bill
|>James Maeding
|>Civil Engineer and Programmer
|>jmaeding - athunsaker - com
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
