DWG path hard coded in file after copying from another project
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have a new issue that just popped up today. We have two teams of people working on the same project at different locations. Each location has a network project that they're working on, each of them have different drives mapped. One is mapped to a drive called T: and one is using P:. The problem is that when copying the files from one location to another and then inserting them into the project, the path seems to be hard coded now into the dwg file. Here's our workflow:
Site 1 works on a file on their network drive mapped as T:
Site 1 places that file on Dropbox for sharing to Site 2
Site 2 copies that file and overwrites the one they have on their drive mapped as P:
Site 2 opens the file, updates the database, closes the file
Site 2 opens the file again, now Plant 3D can't find the file.
Look in Project Manager and the file shows a path to Site 1's T: drive
I can't figure out how or why these files all of a sudden wont' remap to the new location once they're brought into the project. I've tried removing the file and copying it back in. I've tried creating a new project. Still have this problem. The crazy part is that we've done this literally HUNDREDS of times in the past with no issues. Site 1 says they haven't changed anything in their project setup.
We're both running Plant 3D 2018, same versions.
Any ideas?