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

Question

Good Afternoon, I am trying to configure CONNECT so that I can keep the Workspaces on the local drive but to direct the child Worksets to a network drive. That way the standards (and any resource files) are local but the drawings can be accessed by all on the network. 
 The custom location of the WorkSpaces are here: C:\!msCONNECTconf\WorkSpaces (See Custom Folder in screenshot Workspaces.png) 
 I can create the WorkSpace for the Local Drive (See screenshot CONNECT_Open 2.png) 
 
 Afterwards I can create the WorkSpace for the Y:Drive / network drive and create a WorkSet and even a dgn within it, and everything appears normal in the current session of CONNECT, but once I Close CONNECT and try starting CONNECT, it will crash. This what I have for the "Local C.cfg" file: 
 _USTN_WORKSPACEROOT = $(_USTN_WORKSPACESROOT)$(_USTN_WORKSPACENAME)/ _USTN_WORKSPACESTANDARDS = $(_USTN_WORKSPACEROOT)Standards/ _USTN_WORKSETSROOT = C:/PIN/ _USTN_WORKSETSDGNWSROOT = $(_USTN_WORKSETSROOT)/ 
 MS_MACRO > $(_USTN_WORKSPACESTANDARDS)Macros/ MS_VBASEARCHDIRECTORIES > $(_USTN_WORKSPACESTANDARDS)Macros/ _USTN_WORKSPACEDESCR = Workspace used to direct to proper drive 
 And this is what I have for the "Network Y.cfg" file: 
 _USTN_WORKSPACEROOT = $(_USTN_WORKSPACESROOT)$(_USTN_WORKSPACENAME)/ _USTN_WORKSPACESTANDARDS = $(_USTN_WORKSPACEROOT)Standards/ _USTN_WORKSETSROOT = Y:/pin/ _USTN_WORKSETSDGNWSROOT = $(_USTN_WORKSETSROOT)/ 
 MS_MACRO > $(_USTN_WORKSPACESTANDARDS)Macros/ MS_VBASEARCHDIRECTORIES > $(_USTN_WORKSPACESTANDARDS)Macros/ _USTN_WORKSPACEDESCR = Workspace directs to Y drive 
 Is there some trick I am not aware of when creating a configuration in this way? Thanks for your Help and your time,

Tim Hickman · Accepted Answer

I did create a second workspace to look at the network worksets. As a matter of fact I have 4 different workspaces. One of which is pointing to my network for its worksets - which is what the screenshots show. It is loading my workset *,cfg file off of the network location.

Grot · Answer

Tim found the solution! 
 He was able to get my organization's configuration to work with it's particular setup that we have been using since MX. And work around CONNECT's processing time on search path idiosyncrasy. 
 Tim was able to: 
 1. Keep my organizations standards at the Organizational level Local. 
 2. Use the WorkSpace choice as a switch to either work locally or work off a network drive. (We do this because Survey work is best done Locally or because of lack of internet, while working off a network has better access for other disciplines and locations.) 
 3. Only one WorkSpace, the "Local C" WorkSpace has its corresponding "Local C.cfg" file while the "Network Y" WorkSpace only has its WorkSpace.cfg file. (So there are no standards contained at this level for the Network Workspace.) 
 
 *We only have two WorkSpaces "Local C" and "Network Y" 
 4. The local WorkSpace "Local C.cfg" has All configuration variables "active" within its cfg. 
 
 5. The network WorkSpace "Network Y.cfg" has All But One configuration variables "Deactivated" within its cfg. 
 
 This has fixed the issue of CONNECT "hanging up" at startup and locking up the PC. Due to this issue of CONNECT's search path process time, it is best if you follow these guidelines. 
 1. The WorkSpaces should be on the same drive as the Organization and the WorkSets are contained just below the WorkSpace in the file structure. 
 2. Also keep the WorkSet folder, the WorkSet.cfg file, and the WorkSet.dgnws file together (as shown here) 
 
 If your configuration requires you to separate these into separate locations and separate drives and you notice unworkable "hang times" you can attempt to improve this by "Commenting Out" configuration variables with search paths within the WorkSpace.cfg. But REMEMBER by doing so you render the contents in corresponding file path invisible to CONNECT and Will Not Be Read. For my organization this is not an issue because all disciplines use one set of standards and customizations, That is why you don't see a "Network Y" WorkSpace folder partnered with the "Network Y" WorkSpace.cfg file, because they wouldn't be read by CONNECT anyway (because of the way I have the configuration variables commented out in the cfg). 
 
 Hope this Helps! 
 And Thanks Again Tim for your determination and time that you put into this resolution, Peace,

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

Top Replies