In CONNECT how do you direct a Workset to another drive away from the parent Workspace

you also have a forward slash at the end of the   _USTN_WORKSETSDGNWSROOT = $(_USTN_WORKSETSROOT)/   line. In the previous variable definition, it is already pointed to a folder, so the forward slash on the DGNWSROOT should not be needed.

Good Afternoon Tim,

The company's Standards are kept at the Organizational level which would be everyone's PC.  So the two Workspace configurations have very little in them except direction on where their child Worksets are located.  Workspace "Local C" has its Workset location under the "Pin" folder on the "Local Drive / C".  Workspace "Network Y" has its Workset location under the "Pin" folder on the "Network Drive / Y". 

Thank you for your time, 

I just created a workset from the UI with it located out on my network with no issues.

Is it possible that you have a syntax issue or possibly misnamed something ?

Or maybe something wrong with the WorkSpace Dialog box where you set the location of the various files?

I created a new folder on my network and it was empty. I then started Connect Edition. At the start dialog I selected my local workspace. I then selected create workset. In the dialog that opened, I keyed in my new workset name, gave it a description and then selected the browse button for the root folder and picked the empty folder out on my network. Doing this filled in the rest of the options (design files, standards files and standards subfolders). I selected ok and it created the workset. Now since the DGN folder was empty, I had to create a new DGN file. I did this, and then entered the file.

It works for me - I am not able to reproduce the issue. Either doing it manually or thru the dialog.

So Let me get this Straight:

1. You didn't create a second WorkSpace that directs to the Network Drive?

2. You created a second WorkSet within your Original WorkSpace which directs this empty dgn folder on the Network Drive?

Because if the above is true that is not what my problem is.

I looking to create TWO WorkSpaces

One with WorkSets on the Local Drive 

One with WorkSets on the Network Drive.

I used the same method that you used to place the Workset on the network and it did work for me. It is possible that something is not working correctly with your install of MicroStation but MicroStation is capable of doing what you are trying to accomplish. You can try running a repair of your MicroStation installation. I would also suggest that you try creating the workspace and workset from a different computer. That will determine if something is wrong with the installation of MicroStation on your computer.

You said, “The company's Standards are kept at the Organizational level which would be everyone's PC”. Most companies prefer to keep their Organizational level standards on the network. If you need to make a change to the standards (add a level to a level library or make a change to a text style), if the standards are local, you need to make the change to every computer running MicroStation. If the standards are on the network, you make the change on the network and everyone gets the change. It is much easier to maintain. You can also make the folders read-only if you wish.

I used the same method that you used to place the Workset on the network and it did work for me. It is possible that something is not working correctly with your install of MicroStation but MicroStation is capable of doing what you are trying to accomplish. You can try running a repair of your MicroStation installation. I would also suggest that you try creating the workspace and workset from a different computer. That will determine if something is wrong with the installation of MicroStation on your computer.

You said, “The company's Standards are kept at the Organizational level which would be everyone's PC”. Most companies prefer to keep their Organizational level standards on the network. If you need to make a change to the standards (add a level to a level library or make a change to a text style), if the standards are local, you need to make the change to every computer running MicroStation. If the standards are on the network, you make the change on the network and everyone gets the change. It is much easier to maintain. You can also make the folders read-only if you wish.