Community
Civil 3D Forum
Welcome to Autodesk’s Civil 3D Forums. Share your knowledge, ask questions, and explore popular AutoCAD Civil 3D topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Relative Path for Xrefs is FLAKEY!

5 REPLIES 5
Reply
Message 1 of 6
CADD_Maven
468 Views, 5 Replies

Relative Path for Xrefs is FLAKEY!


Does anyone else experience this in Civil 3D 2008 SP2 or later? When attaching an external reference as an overlay WITH relative path, AutoCAD warns that "relative path can not be assigned", and then defaults to full path. However, if I go to the xref manager and manually change the saved path to a relative notation (ie .\ or ..\), the path changes to relative and stays that way with no problems. Why on earth would AutoCAD insist that it's not possible and then allow it. This is ludicrous. I can not replicate the problem. It's very sporadic. BTW - There are no similarly named xrefs or blocks, so I doubt this has anything to do with reference name conflicts.

5 REPLIES 5
Message 2 of 6
Anonymous
in reply to: CADD_Maven



This will occur if the current file has not been saved
prior to the xref command


 


From Help
name=WS1a9193826455f5ff15eac7f10e40671dc3-77c5>


Path Type



name=WSc30cd3d5faa8f6d815ee671ffc2d62ae1-7ffc>
Specifies whether the
saved path to the xref is the full path, a relative path, or no path. You must
save the current drawing before you can set the path type to Relative Path. For
a nested xref, a relative path always references the location of its immediate
host and not necessarily the currently open drawing.



name=WSfacf1429558a55de8b299cffc1fb20d35c>
 



--
Thanks, Joe

 

Joseph D. Bouza, P.E.
Civil 3D 2008
LDT 2008
Win XP pro
v 2002,
sp 2
hp workstation xw4600
Intel Core Duo CPU
E7200 @2.53 GHz
3 GB
RAM
NIVDIA Quadro FX 1700 (512MB)

 

The mantra of a former Flamer:

 

If you are forced to eat an Elephant, don’t complain about it; Take one
bite at a time.

 

*****************************************************************************************
In
memory of the King of Work-arounds
"The only Constant is Change".

 

"The only thing worse than training your staff, and having them leave is
-
not training your staff, and having them stay." 😮
A reminder taken
from Graphics Solution Providers' Calendar
page
*****************************************************************************************


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">


Does anyone else experience this in Civil 3D 2008 SP2 or later? When
attaching an external reference as an overlay WITH relative path, AutoCAD
warns that "relative path can not be assigned", and then defaults to full
path. However, if I go to the xref manager and manually change the saved path
to a relative notation (ie .\ or ..\), the path changes to relative and stays
that way with no problems. Why on earth would AutoCAD insist that it's not
possible and then allow it. This is ludicrous. I can not replicate the
problem. It's very sporadic. BTW - There are no similarly named xrefs or
blocks, so I doubt this has anything to do with reference name
conflicts.

Message 3 of 6
CADD_Maven
in reply to: CADD_Maven

Thanks, Joe. Do you mean "has not been saved" as in "must be saved with a file name and not just a new drawing from .dwt template" or do you mean "must hit save every time before xrefing anything with a relative path"? My file has been saved with a file name already, but the problem happens any how. Does this mean I need to hit save right before attaching an xref with relative path? If so, I call that a bug!



Sometimes it's good to get a consensus on these "quirks" to know if I'm just doing it wrong or if it really is a bug. Thanks for your help.









"The razor thin line between bug and feature is the fuel that drives the engine of progress forward... very very slowly."
Message 4 of 6
AdammReilly
in reply to: CADD_Maven

Generally it means must be saved with a file name.
Also, relative path doesn't work if your xref is on another drive letter than the file your in.

Adam Reilly

Dell Precision 55400
Windows 10 Pro
Intel Xeon E-2276M 2.80GHz, 64bit
NVidia Quadro T2000 Mobile/Max-Q


LinkedIn | Twitter


Group Leader badge


Austin CADD User Group


LinkedIn | Discord

Message 5 of 6
Anonymous
in reply to: CADD_Maven


Oops I left that part out. Thanks


--
Thanks, Joe

 

Joseph D. Bouza, P.E.
Civil 3D 2008
LDT 2008
Win XP pro
v 2002,
sp 2
hp workstation xw4600
Intel Core Duo CPU
E7200 @2.53 GHz
3 GB
RAM
NIVDIA Quadro FX 1700 (512MB)

 

The mantra of a former Flamer:

 

If you are forced to eat an Elephant, don’t complain about it; Take one
bite at a time.

 

*****************************************************************************************
In
memory of the King of Work-arounds
"The only Constant is Change".

 

"The only thing worse than training your staff, and having them leave is
-
not training your staff, and having them stay." 😮
A reminder taken
from Graphics Solution Providers' Calendar
page
*****************************************************************************************


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
Generally
it means must be saved with a file name. Also, relative path doesn't work if
your xref is on another drive letter than the file your
in.
Message 6 of 6
kkuecker-traffic
in reply to: Anonymous

I have also had this problem if I am trying to attach a reference from our company network drive, but my drawing was saved on my hard drive.

 

When I save the drawing on the network, I have no problem attaching with relative path.

Intel Core i5-2500K CPU @ 3.30 GHz
8.00 GB
64-bit

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Rail Community


 

Autodesk Design & Make Report