We are having a strange occurrence. When attaching a reference to a dgn file outside of the current folder ORD will be attached the wrong dgn.
For example, we have a drawing named topog.dgn. When trying to attach to a different "topog.dgn" file from a different project- after the file is selected in the ref dialog box and you select ok. The reference is created to the open topog.dgn file.
Has anyone else had this problem?
We are using OpenRoads Designer ED 2022 R1.1. (10.11.3.2)
You can create custom variables that point to other folders and make them part of the workset cfg file. For example, if you define a set of variables, such as Project_A and Project_B, you can reference files using Project_A: or Project_B: to force MicroStation to look in the folders pointed to by those variables. There is even a Directory button to select a folder by its variable name - Select Configuration Variable...
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
When a CADD Standard create problems, it is time to revisit those standards. Unique filenames are possible with not a lot of work. All that needs to be done is to add a project identifier to the filenames. With Open Roads files being both CAD files and design data containers, we even added a corridor name to our standard file names, All files within a project get a project ID associated with them and are part of the filename and when a file contains design data, if it is specific to a particular road in the project, we define a "corridor" name, to be used for alignments, superelevation, corridors, terrain elements and more.
This way, reference filenames are always unique per project and referencing files across projects are never an issue.
Chuck:
We do much the same here; project numbers being the primary designator. So, we might have 12345_corridor.dgn, 12345_Terrain.dgn, 12345_Topo.dgn, etc. We have a default template which defines this structure and which gets copied into each WorkSet.
Best Regards,
Mark