Wednesday, 07 December 2016
  4 Replies
  2.8K Visits
0
Votes
Undo
  Subscribe
I modified the width of my detail frame and now am having trouble getting the DETAIL-FILE field to appear as it should. It is still right justified and it appears in the correct location in model space of the DWG (see attached), but when I place it on a sheet, it reverts to the original location (see other attached file). What am I doing wrong?
Accepted Answer
0
Votes
Undo
The issue in this drawing appeared to be corruption causing a command in the place detail tool and update details to misfire.

The solution was:

In OPTIONS, go to the "Open and Save" tab. Under "Object ARX Applications", set Demand load ObjectARX apps to "Command Invoke" and turn on "Show Proxy Information Dialog Box". Click OK and restart AutoCAD. This turns on the proxy information dialog box so all potentially corrupting proxies can be seen. This box will pop up when a drawing is opened. In this case, there were almost 1000 proxies, with many being a particularly corrupting "Autodesk Architectural Desktop 2007" proxy graphic. These are known to jump between drawings even without an xref link.

The drawing needs cleaning. It's always best to either NUKE or manually clean any consultant drawing coming in before you xref. For existing drawing like this, first clean all xrefs, closing AutoCAD completely and reopening to clean each new file. This prevents those 2007 proxies from jumping between drawings an re-infecting drawing you just cleaned. Then at the end, manually clean your own drawing.

Here are our handy cleaning steps, including links to the NUKE tool and Manual Cleaning Steps.

Cleaning Your Drawings & Xrefs:
https://www.landfx.com/index.php/docs/cad-basics/autocad-getting-started/item/2616-clean.html

Drawing Corruption Explained:
https://www.landfx.com/kb/autocad-fxcad/files/item/2617-corruption.html

Preventing Drawing Corruption:
https://www.landfx.com/index.php/docs/cad-basics/corruption-primer.html

Thanks,
Amanda
Hi Katherine,

It looks like your detail-file attribute may have gotten the wrong justification accidentally assigned to it. Double check in its properties that it's justified to the right.

Thanks,
Amanda
7 years ago
·
#843
0
Votes
Undo
I double and triple checked. It's definitely right justified.
Ok! I'll need you to send in the detail file in with a technical support ticket so we can have a look.

https://www.landfx.com/support.html

Thanks,
Amanda
Accepted Answer
0
Votes
Undo
The issue in this drawing appeared to be corruption causing a command in the place detail tool and update details to misfire.

The solution was:

In OPTIONS, go to the "Open and Save" tab. Under "Object ARX Applications", set Demand load ObjectARX apps to "Command Invoke" and turn on "Show Proxy Information Dialog Box". Click OK and restart AutoCAD. This turns on the proxy information dialog box so all potentially corrupting proxies can be seen. This box will pop up when a drawing is opened. In this case, there were almost 1000 proxies, with many being a particularly corrupting "Autodesk Architectural Desktop 2007" proxy graphic. These are known to jump between drawings even without an xref link.

The drawing needs cleaning. It's always best to either NUKE or manually clean any consultant drawing coming in before you xref. For existing drawing like this, first clean all xrefs, closing AutoCAD completely and reopening to clean each new file. This prevents those 2007 proxies from jumping between drawings an re-infecting drawing you just cleaned. Then at the end, manually clean your own drawing.

Here are our handy cleaning steps, including links to the NUKE tool and Manual Cleaning Steps.

Cleaning Your Drawings & Xrefs:
https://www.landfx.com/index.php/docs/cad-basics/autocad-getting-started/item/2616-clean.html

Drawing Corruption Explained:
https://www.landfx.com/kb/autocad-fxcad/files/item/2617-corruption.html

Preventing Drawing Corruption:
https://www.landfx.com/index.php/docs/cad-basics/corruption-primer.html

Thanks,
Amanda
  • Page :
  • 1
There are no replies made for this post yet.