Zortar
12-12-2011, 04:24 PM
I ran into a problem recently with AutoPlant V8i that is causing us some problems at our company. First off, we use UNC paths in Document Manager since we have duplicate drive letters in our various offices. In previous versions, if a user needed to rename or move a model they would use the Relationship Manager. In V8i (all releases) we've found that this no longer works with UNC paths since the DWG file is not completely updated with the new file name. Specifically, the variable AT_REBIS_APP_DB_NAME which is stored in the drawing doesn't get updated to the new file name. When you try to open the drawing you receive an error saying the drawing is already registered in the project.
You can see the incorrect value for the variable above by first disabling the loadpiping.scr which is automatically loading the Piping software. Either rename it temporarily in the %Network_Root%\SUPPORT folder or change the line in AT.INI that loads it. Open the drawing in AutoCAD from Document Manager and then type:
(at_dwgdata_getfldlist "at_rebis_app" "at_rebis_app_db")
You will see the old drawing name listed with an MDB extension. You can change the variable by typing.
(at_dwgdata_setfld "AT_REBIS_APP" "AT_REBIS_APP_DB" "AT_REBIS_APP_DB_NAME" "C" "newname.MDB" 1 1)
Make sure your newname.mdb has the correct path.
In short, I would recommend using drive letters instead of UNC paths until (if) they get this fixed.
You can see the incorrect value for the variable above by first disabling the loadpiping.scr which is automatically loading the Piping software. Either rename it temporarily in the %Network_Root%\SUPPORT folder or change the line in AT.INI that loads it. Open the drawing in AutoCAD from Document Manager and then type:
(at_dwgdata_getfldlist "at_rebis_app" "at_rebis_app_db")
You will see the old drawing name listed with an MDB extension. You can change the variable by typing.
(at_dwgdata_setfld "AT_REBIS_APP" "AT_REBIS_APP_DB" "AT_REBIS_APP_DB_NAME" "C" "newname.MDB" 1 1)
Make sure your newname.mdb has the correct path.
In short, I would recommend using drive letters instead of UNC paths until (if) they get this fixed.