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?
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.
We have set up our configs on a network (Workspace and Workset ASCII files, Standards, etc.), but each user's session changes the Projects.dgnws file independantly per sesssion. This only requires one small change to C: drive ConfigurationSetup.cfg.NB. Their own changes save to local disc, Personal.cfg.FWIW. I am not sure whether this contributes somewhat to our crash rate.It would be a good thing to be able to send any User Automatically generated files, based on Company WS, to the user's local file location to avoid this conflict.We do not see a problem with user's changing other's look and feel however, it seems to just be a conflict of file last saved date/time.Bentley, It would be good to know this will not cause us trouble in future though.
Greg SmithAirways New Zealand
There should be one DGNWS per WorkSet written to by all users of that WorkSet.
If you can tell us more about how you have set up your Configuration we can advise further.
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.