File Structure and Xref Paths

[Anonymous]

Hello,

I work for a company that is looking to change the file structure of our project database. It is to my understanding if we change the folder names on our share point, then the drawings that are referenced in said folder will lose their paths if referenced in other drawings. Is there a way around this other then selecting new paths for all the references? There are thousands of project folders that need to be renamed so selecting new paths to every drawing that contains references is not feasible. 

Thanks

[rkmcswain · Accepted solution]

The answer is "it depends".

If you are using relative paths, and the renamed folder is not part of the relative path, then you're in good shape, nothing will be required. For example, if your folder structure is like this:

Then the relative path to the Xref may be something like this: ( .\Xref\Child.dwg ) - so that if the folder named "SubProject" was renamed to "XXXX" - it would still work. See screenshots below. Folder was renamed, no action was taken to get Xref to show up after folder rename.

But if that is not the case, you could make use of the Reference Manager to bulk change the paths, one project at a time.

[jrreid · Accepted solution]

I say don't make it hard on yourself or others.

There is no reason to separate the XREFs from the DWGs.

If they are in the same folder it will load not matter what the Z:\XX\XX\XX was.

We used US ARMY Corp at the beginning and it has never let us down for losing XREFs.

We have other projects that we setup a little different, but again, all XREFs stays with the DWGs. 

Hope this helps.

JRR.

ARMY CORP NAMING:

OTHER PROJECTS NAMING:

[3wood · Accepted solution]

My suggestion is do not worry about the file structure changes, just get the IT guy to set up a " Virtual Driver" for you.

https://sites.google.com/site/cadkits/autocad-tips/how-to-keep-original-xref-structure-in-a-new-comp...

[rkmcswain]

@jrreid wrote:

There is no reason to separate the XREFs from the DWGs.

Actually, there is. If multiple groups, departments, etc. are referencing the same DWG file(s) into various projects, you typically would not want to combine DWGs from multiple projects in the same folder.

[RSomppi]

---

@jrreid wrote:

There is no reason to separate the XREFs from the DWGs.

---

There are plenty of reasons. If your okay all your files in one folder, that's fine, but that doesn't mean there is no reason for others to have structure and organization.

[jrreid]

Not to step on toes or make waves, but it can also be said... Rkmcswain gave his reasons and I respect that.

But if one does not need separated folders for XREFs then there is no reason to separate them..

and yes, I do like all my files in one folder... as do most Government Standards requires, it is organized, no XREF hiccups.. I still use OVERLAY and RELATIVE PATH... But that is the beauty of AUTOCAD... there are so many different ways to set it up, draw it up and as most would say their way is the best way as I could tell in how RSomppi came back with comments and that is ok too. I enjoy some steam in these comments once in a while.

With that said...I would love to take a survey and I bet Most company setups don't separate their XREFs.

But that would be in a different category.

JRR.

[RSomppi]

---

@jrreid wrote:

most would say their way is the best way as I could tell in how RSomppi came back with comments

---

I said no such thing. I was merely pointing out that there are plenty of reasons. Organization and structure are just a couple. If you can live without those fine, but saying there is no reason for them is, well, obtuse.

[Anonymous]

@RSomppi Exactly. Our company has multiple projects for the same customer and even in the same location. So we separate as built and master drawings in a separate folder so that they maybe be referenced by all projects and not tampered with on a project to project basis.