Announcements
IMPORTANT. Forum in Read Only mode. You can no longer submit new questions or replies. Please read this message for details
Autodesk Architectural Desktop 2007 & Prior
Welcome to Autodesk’s Autodesk Architectural Desktop 2007 & Prior Forums. Share your knowledge, ask questions, and explore popular Autodesk Architectural Desktop 2007 & Prior topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Errors w/ drawing that has an Xref attached

2 REPLIES 2
Reply
Message 1 of 3
Anonymous
129 Views, 2 Replies

Errors w/ drawing that has an Xref attached

We just started using ADT r3.3 this is one strange error
a few people have gotten.

When they open a drawing that has an xref attached this is what they get after the software initilizes?

Do you really want to do this?
Do you really want to do this?
Do you really want to do this?

It repeats the above quite a few times and then
everytime you try and type in a command it repeats
the message above? Then (this is a good one) it
copies the x-ref file into the drawing as a block
and explodes the block? So now you have the x-ref
file still attached and a block of the x-ref on top
of it exploded? I thought I fixed the problem by
blocking out the x-ref and the drawing file into a clean template. Then a few days later the problem came back?
Any ideas??????

Jeff S
2 REPLIES 2
Message 2 of 3
cphubb
in reply to: Anonymous

Jeff,

We are also having that problem. When we experience that error, ADT also places the xref block in paperspace full scale, and corruptes the PS block so that we need a full recovery and resave. Worst case we needed to dump our sheet file and recreate it from the original base file.
We feel the cause of this is hatching using the hatch boundry to ADT objects like elevations sections, then xrefing that drawing into another. We have found that hatching to a pline on a non-plotting layer prevents those errors from happening. Although it may seem that drawing a pline for all hatches is time consuming it really saves time when the elevations/sections update. We just stretch the pline around a little and the hatch is fixed. We have also noticed fewer crashes when we hatch that way.
I would like to see if anybody else has had similar problems or if Adesk know the problem.

Chris H
Gabbert Architects Planners
Message 3 of 3
Anonymous
in reply to: Anonymous

Do not use an ADT element (such as a wall) or an XREF as the boundary for associative hatching. Either use non-associative hatching or use a polyline (on a non-plotting layer, if desired) as the boundary. You can set the BHATCH command to retain the boundary as a polyline on the Advanced tab, in the Object type area.

--

David Koch

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

Post to forums  

Autodesk Design & Make Report