Today I got a new wrinkle. Not only do I need to get OpenRoads up and running, there will be people using MicroStation Connect who will need the same workspaces.
If the Client standards were stored by default in the Workspaces, this might not be so bad. That would just require me to make sure that ConfigurationSetup.cfg pointed to my network and WorkspaceSetup.cfg directed to my workspaces. But no. All but one of my clients store their standards files in Organization-Civil, which plain MicroStation doesn't know exists.
My instinct is to copyMY_CIVIL_ORGANIZATION_ROOT = M:/Bentley/ORD/Configuration/Organization-Civil/into my WorkSpaceSetup. I think that would be sufficient for the client standards to show up.But am I mistaken?
How do you folks combine Mstn & ORD workspaces so that they both see the same resource files?
I have MicroStation use the exact same WorkSpace and WorkSet configuration files as ORD from the same location.
MicroStation will load all of the resources (except the ORD-specific ones) just fine.
Haven't had a problem with it.
Rod WingSenior Systems Analyst
Answer Verified By: MaryB
Glad to hear it. I figured it would just ignore them, but ya never know.Thank you.
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
I do the same as Rod. I usually cheat and use MicroStation for a lot of batch processing because it loads for me so much faster.
All the extra variables (all the CIVIL_ variables) are ignored by MicroStation. So far including ORD dgnlibs in MS_DGNLIBLIST hasn't caused any issues for me, and makes sure things that do work in both like levels, are all there.
Glad to hear that. We don't use plain Microstation often, but there are some folks in other departments who do. They still need the DOT standards for some of their projects. i imagine half the time they will go No Workspace/No Workset, but I want the capability to be there for the proper standards when they do need them.