I'm running into a issue when running several different Workspaces that configuration variables that are defined in one workspace are showing up in the active workspace. If the active workspace doesn't define or redefine the variable the variable will be defined by any previously used workspace. Is there anyway to prevent this from happening or the have all variables removed and only define those that are in the active workspace. This would include all levels Organization, Workspace, and Workset.
Hey Mike... What version of the software are you running? Any specific client workspaces you're frequently using?
Bentley Accredited Road Designer | Bentley Accredited Road Modeler
colliersengineering.com
This is a known issue. Safest bet is to close OpenRoads altogether when switching.
Robert Garrett Senior Consultant
www.envisioncad.com
Microstaion CE 10.16.00.08
OpenRoads Designer 10.10.21.04
It doesn't seem to matter. The variables that are causing the problems came from a workspace I only used once. They persist even after restarting my computer.
In the Configuration Variables dialog box, what "Level" does it attribute to the variables? WorkSpace, WorkSet, User, etc.
We sometimes define custom variables for different Workspaces and then, within each different WorkSpace, assign built in variables using these custom variables.
This way, when you switch WorkSpaces, the new WorkSpace will redefine the built in variables with different custom variables.
Since moving to the CONNECT products, there are very few places we need to do this. Between the Organization, Civil-Organization, WorkSpace and WorkSet variable assignments built into the Workspace, many of our traditional customization of CFG files are no longer needed.
In V8, users often made edits written to a UCF that broke parts of a Workspace. While it can still happen, its not as common since there is little reason to use a UCF to tweak a workspace, In V8, since there was no Organization (Client) configuration built into the system, some offices used UCF files to manage clients.
Look into creating MSDEBUG.txt files. They are my go-to tool for trying to diagnose issues. Using Notepad++ with its compare files add-in makes it easy to see what is different between two workspaces and can help figure out where an assignment seems to be getting made that should not exist in a different workspace.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
what you have stated is too generic.
I agree that a DEBUG would help shine some light as to what is going on in your configuration.
How to Quickly Generate a Debug File
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691