We are using Power InRoads V8i, Select Series 2.
We have been developing our InRoads XIN file and levels on a stand alone system. When we provide a new Project Default and associated pathing that is directed to a project on our network server, the levels are not available and the Project Default paths do not appear to be respected (ie: does not open on Project Default Directory path but are forced to browse to it each time). Any thoughts on what the likely reason is for this type of performance?
Post some screen shots - make sure they are legible.
We use Project Defaults with workspace variables and have no issues with it. When one of my uses selects the Project in the MicroStation Manager before opening a file, the proper InRoads files are automatically loaded.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
The attached post shows the Project Defaults directing the project paths to the "L" drive. However, when opening the InRoads program, the options I get to open a project are directing paths to my "C" drive. Since I posted this, have been able to get my layers imported to view from my "L" drive project, but still wonder what configuration file controls these paths, appears to be saved with the proejct? Have similar problems with my text styles: unable to view them on my project on "L" drive but can only view them on project located on "C" drive. There seems to be a disconnect between Microstation elements (layers and text styles) and InRoads Projects, as well as, pathing for the project.
Thanks again for your help on these questions.