Object Enabler /R14 vs ADT3.3 help

[JamesJewett5856]

Working in a mixed ACAD environment along with working with consultants who are not on the ADT3.3 platform presents a real challenge to me. Since we have a mix of r14, ADT2.0, ACADlite200i and ADT3.3 (thanks to budgetary constraints at this time) we need to save down to r14 format in order for anyone to open/edit a drawing. However I've noticed that ecent with the Object enabler installed on r14 (OEv1.22 as per Autodesk) Wall objects do not show proper intersections (interference icons show and the intersections are messy).

I'm experimenting with other objects but my question is: Am I using the correct enabler? Also I have these problems I'm facing: 1)we cannot do multiple layout drawings in ADT3.3 since the savedown to r14 only displays the last current layout (i.e. 3 drawings in one file save down to only 1 in r14) 2)ACADLite2000i does not have a LMAN feature, so any layer states saved in ADT3.3 do not carry over to Lite. 3) The problem with Xrefs being un-resolved when saved down to r14, then attempted to in in ADT3.3 - we need to do an Audit in order to purge the blasted "" block name....Oh to be rich and move everyone to one system!

Jim - frustrated IT/CAD Manager...

[Anonymous]

Jim,

Funny you mention this now, I just got off the
telephone with a consultant who is in the same predicament.  You are using
the correct enabler, however this has limitations (taken from the
website):

"Review the information below for steps
required to transfer the file.

size=2>

Drawings MUST be saved in R14 format before being transferred to the recipient. This process may cause the appearance of some AEC objects to change or data associated with AEC objects to be lost, therefore Autodesk recommends using the AecObjectExplode routine to preserve the visual fidelity of Arch objects. The recipient can install the Object Enabler version 1.22, which will enable Arch objects from Architectural Desktop R1.0. Associative dimensions will function as non-associative dimensions in this environment but will be restored if the drawing is returned to an AutoCAD 2002-based product or a product on which the AutoCAD 2002 Associative Dimensioning Object Enabler is installed. " It looks like to work with ADT 3.3, and to use the OE you need at least 2000i or higher to work together, or else you run into what you are seeing now.  I have tested this out using the OE 3.30 and it works quite well. class=leafPageHeader>  class=leafPageHeader>-Beau

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

"jjewett" <jjewett@jhn.com>
wrote in message
href="news:f0fdbde.-1@WebX.maYIadrTaRb">news:f0fdbde.-1@WebX.maYIadrTaRb...

Working
in a mixed ACAD environment along with working with consultants who are not on
the ADT3.3 platform presents a real challenge to me. Since we have a mix of
r14, ADT2.0, ACADlite200i and ADT3.3 (thanks to budgetary constraints at this
time) we need to save down to r14 format in order for anyone to open/edit a
drawing. However I've noticed that ecent with the Object enabler installed on
r14 (OEv1.22 as per Autodesk) Wall objects do not show proper intersections
(interference icons show and the intersections are messy).

I'm experimenting with other objects but my question is: Am I using the
correct enabler? Also I have these problems I'm facing: 1)we cannot do
multiple layout drawings in ADT3.3 since the savedown to r14 only displays the
last current layout (i.e. 3 drawings in one file save down to only 1 in r14)
2)ACADLite2000i does not have a LMAN feature, so any layer states saved in
ADT3.3 do not carry over to Lite. 3) The problem with Xrefs being un-resolved
when saved down to r14, then attempted to in in ADT3.3 - we need to do an
Audit in order to purge the blasted "" block name....Oh to be rich and move
everyone to one system!

Jim - frustrated IT/CAD Manager...

[Anonymous]

OE 1.22 was built to handle ADT release 1 objects. It will handle some objects
from later releases, but only in a dodgy (and unsupported) fashion. There is no
other R14 object enabler. For what it's worth, I'd try to convince whoever's in
charge of the purse strings that the wasted time and potential for disaster due
to conversion errors is worth the cost of an upgrade.