ARX_ERROR in ADT4 to ADT3 conversion

[JamesVan]

When we save files back to DWG 2000 format from ADT4, either with Save As or the Batch Drawing Converter, we frequently get the following errors in ADT3.3:

ARX_ERROR: eLockViolation
ARX_ERROR: eNotThatKindOfClass

The only way to resolve this is to WBlock the entire drawing into a new file in ADT3.3.

At other times, Mtext entities completely disappear. Has anyone suffered through the same experience?

[mjfarrell]

Export is working exactly as designed by AutoDesk
to foster older version user into upgrade due to
design interoperability issues.

A partial from the link below
<snip>
Additionally, if you use Autodesk Architectural Desktop 3.3 or older to open an Autodesk Architectural Desktop 2005 file that has been saved in AutoCAD 2000 DWG format, a dialog box is displayed with the following warning:

This application has detected objects from a newer version in this drawing.

Some commands will not be available.

Save this drawing from the original application as AutoCAD 2000 format either with the AEC objects exploded, or with the ProxyGraphics turned on, and attach it as an Xref in order to use it as a background.

In addition to this warning, a number of ARX_ERROR: eNotThatKindOfClass messages will be repeated on the command line. Once the file is opened in the previous release, all Autodesk Architectural Desktop commands will be disabled for the remainder of the session.


http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=4136743&linkID=2476059

[richard.binning]

When we save files back to DWG 2000 format from ADT4, either with Save As or the Batch Drawing Converter, we frequently get the following errors in ADT3.3:

ARX_ERROR: eLockViolation
ARX_ERROR: eNotThatKindOfClass

The only way to resolve this is to WBlock the entire drawing into a new file in ADT3.3.

At other times, Mtext entities completely disappear. Has anyone suffered through the same experience?
You will need to use the "Export to AutoCAD" function to save files back for use in previous versions of Architectural Desktop. This is not due to some evil plot to force an upgrade it is simply a matter of the previous application not understanding some of the new capabilities, properties, or methods of Objects upgraded or created in the newer versions. You WILL NOT be able to maintain objects, styles, etc when going back to ADT 3.3 or newer.