Question 1 - Is it possible to share the same WorkSets between MicroStation CONNECT, PowerDraft CONNECT, OpenRoads Designer, etc. without corrupting the .dgnws file?
That is have all of these CONNECT applications use the same _USTN_WORKSETSROOT location?
Question 2 - If a consultant creates Link Sets and Sheet Indexes in a WorkSet, can they send their .dgnws file along with the dgn's back to the client to retain the links and idexes?
2. Don't know, will have to discuss with colleagues.
Did you ever get an answer on this? I'm trying to set up OpenRoads Designer and MicroStation CONNECT and keep getting prompted to change workset depending on which program I use (ORD workset names are different than CONNECT names).
Is there a reason you don't share the same worksets between ORD and MSTN? We have ours setup to do this and aren't seeing any noticeable issues. We actually share all of the configuration.
Thanks John, that's good to know. I'm in the early stages of configuring CONNECT and ORD and wasn't sure if sharing worksets\workspaces was an option. All the info I've found shows the setup for either ORD or CONNECT, never mentioning a mixed environment.
It was setup this way prior to me and I believe by Bentley so I am thinking its a legit way to configure the applications together.
For reference this really doesn't answer the second question by Rod. I forget how the pathing is stored for a sheet index. It may store the path as both Full and Relative. If it stores relative then it should be portable.
Any news on Question 2?
Thanks for the reminder.
LinkSets are stored in DGNLIBs defined by MS_DGNLIBLIST_LINKS, they are portable.
A complete set of folders/files including a DGNWS should also be portable. I know I have moved projects from drive to drive and the DGNWS information has been retained, I have not tested sending a DGNWS and files as described.