Working off a networked Workspace for one specific client (we do outsourcing), our current setup is through the mslocal.cfg pointing to the shared workspace.
However in future each new Client is highly likely to have their own Workspace with own standards and Datasets etc.
Editing the mslocal.cfg for each Client Workspace does not seem very practical although for the moment I cannot find any other way....Any suggestions out there?
Why do I get moderator warning when I try and post here???
Probably I misunderstood. As you are trying to have different workspaces, our approach might not work. We do have different project setups, which do use different datasets.
But a dataset is not the same as a workspace, as datasets still have a common "standards" folder, for example.
In this case I would propose to make copies of the shortcuts of the programs, and change them accordingly. If I am not mistaken you have to add -wrPATH\TO\WORKSPACE to the shortcut.
P.S.: A windows system variable in windows control panel - system.
All my workspaces read the same standards
My users then read different datasets
Ustn since 1988SS4 - i7-3.45Ghz-16 Gb-250/1Tb/1Tb-Win8.1-64bEric D. MilbergerArchitect + Master Planner + BIMSenior Master Planner NASA - Marshall Space Flight CenterThe Milberger Architectural Group, llc
Actually what I finally find works well is to have different mslocal.cfg -one for each Client's workspace - and then add
-wc"PathTo mslocal_XYorZ.cfg" straight after (almost, needs a space) the -ws BB_DISCIPLINE statement...
in the shortcut target for each shortcut. Can't think of another way to launch the software with a choice of Workspace.
Eric, understand your way but I do need full independant Workspace per Cient, each have their own standards etc.