Multiple workspaces - configuration

We do it by setting the Windows variable _USTN_WORKSPACEROOT to the networked workspace.

This is the only thing which is done on the client, the rest is configured on the server.

No need to do anything when a new Microstation is installed on the client either.

I mean i want each user to have the choice of workspace - choose between 4 or 5 diferent workspaces typically...

What do you mean by "Windows" variable anyway?

Actually I can create ABD icons which will deal with specific workspaces so I guess that maybe the easiest... Just configure the target in the shortcut to account for various mslocal_X.cfg files. Not pretty but works.

I use the USER.cfg files as they work per client very well with each having their own Dataset, directory for files etc.  And I can set up many jobs for each client, project, year etc.

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.

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

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.

Andreas, still completely unclear on your Windows Control Panel thing - aside from the fact that I am reasonably happy with my solution of individual shortcuts, still curious...

Chris, hope this screenshot makes it clear, even if it is from a norwegian Windows 7 system.

Edit Control Panel - System - Advanced - Environmental Variables - System Variable - New - USTN_WORKSPACEROOT

Thanks for the screenshot Andreas, understand. Interesting way to do, first time I come across that one.