Request:

I would like to ask that the ability to open OBD & OBM files without a WorkSpace/WorkSet be allowed. ORD has this ability, OBD/OBM should too.

Reason:

Being able to open a file, especially a .dgnlib, without a WorkSpace/WorkSet is very useful when creating new WorkSpaces (Configuration) or editing them. This is also a recommendation for some workflows.

Example:

We have discovered a problem in one of our WorkSpaces, (we are investigating if it could be in other WorkSpaces,) whereby a “geotechnical connection” existed in lots of the WorkSpace files. This connection presumably is used by the gINT tools. No one knows from whence it came. If it exists in any workspace file, it will immediately attach itself to any file as soon as you open it. Thus, it spreads thru the entire workspace as files are edited.

We needed to open the .dgnlib’s, .cel’s and other files, and run a Key-In to clean the files. We needed to open these files, without the infected WorkSpace files. We were able to do this with the ORD files but not the OBD/OBM files.