ObjectARX Enabler

[h.jobe]

How do you know which type of enabler you need to install in order to see the appropriate proxy graphics?

I should note that I know which proxy is causing the problem - it shows up as a rectangle with an "x" through it. I just don't know which program created it.

[RobertB]

That's a good question. I presume you cannot ask the original author of the drawing? If not, can you post the drawing with nothing but the proxy object(s)?

P.S. Are you related to Ed?

[h.jobe]

Hit me with your best shot.

And, yes, I'm his daughter.

[rkmcswain]

Is your PROXYNOTICE set to 1?

72205

My guess would be Architectural Desktop, but I'm not too familiar with its application names, so that may not be it. I'm sure someone will come along to confirm or correct.

[RobertB]

That was pretty easy... it is RText which is an Express Tool. Get Ed to install Express Tools on your computer (and tell him "hi" from Bob Bell!).

[RobertB]

That was pretty easy... it is RText which is an Express Tool. Get Ed to install Express Tools on your computer (and tell him "hi" from Bob Bell!).Although... why anybody is actively using RText now is beyond me... aside from the XRefs feature (why Fields doesn't have that yet is also beyond me.)

[rkmcswain]

That was pretty easy....
Although... why anybody is actively using RText now is beyond me... aside from the XRefs feature (why Fields doesn't have that yet is also beyond me.)

Talking to yourself again huh...? ;)

Back to the topic, I didn't get the proxy notice about the RTEXT since mine was loaded and it didn't occur to me that this was RTEXT, for reasons you mentioned above...

[h.jobe]

Well, the express tools solved one problem - thanks for that.

However, it appears that I have another proxy hiding in the drawing that I can't find. The proxy info that pops up when I open the drawing tells me that the missing application is aecbbldsrv40. There's not a lot of info to be found by doing a simple search about this particular application. Aec is usually an autocad architecture prefix, am I correct?

[RobertB]

However, it appears that I have another proxy hiding in the drawing that I can't find. The proxy info that pops up when I open the drawing tells me that the missing application is aecbbldsrv40. There's not a lot of info to be found by doing a simple search about this particular application. Aec is usually an autocad architecture prefix, am I correct?You need to install the object enablers for both Architectural and then MEP. You need to install Arch first, then MEP.

AecbBldSrv40 is part of the MEP vertical which is based on the Architectural vertical.

However, you need to be running a version of AutoCAD that matches or exceeds the version of the original MEP file (4.0 is pretty old, 5.5 is 2008's version). MEP objects are usually upgraded each release and are not downwards compatible, despite the 3-year cycle for DWG formats.

[RobertB]

Talking to yourself again huh...? ;)Um... yes. (No! Bob, don't answer that!) Shut up! :screwy:

[Ed Jobe]

You need to install the object enablers for both Architectural and then MEP. You need to install Arch first, then MEP.

AecbBldSrv40 is part of the MEP vertical which is based on the Architectural vertical.

However, you need to be running a version of AutoCAD that matches or exceeds the version of the original MEP file (4.0 is pretty old, 5.5 is 2008's version). MEP objects are usually upgraded each release and are not downwards compatible, despite the 3-year cycle for DWG formats.
What if someone with a current version (i.e. the same as Helen) of MEP opened the file and saved it? That should upgrade the proxies and then a current OE should work fine.

[scott.wilcox]

Installing the architectural and MEP object enablers should display the proxies, even if created in an older version. That's my guess anyways, Ed.

[Ed Jobe]

Installing the architectural and MEP object enablers should display the proxies, even if created in an older version. That's my guess anyways, Ed.
Perhaps I misunderstood what Bob was saying.

[Mamma Jamma]

Be careful with proxy objects and multiple versions of AutoCAD/MEP!
We have ACAD, ACAD LT and MEP.
The last time we upgraded, which took months, we figured, "upgrade the LT folks first, they'll cause the least trouble when saving back to the previous version". WRONG.
The Object Enablers used by the newer software messed up the objects so that the MEP people with the older version, the actual creators of the original drawings and entities, couldn't even see them. The objects had been redefined, even though the only things done in the drawings were opening, revving up the titleblock, and saving. Created quite a mess.
We're doing it the other way now. MEP is getting upgraded first, LT last.

[RobertB]

What if someone with a current version (i.e. the same as Helen) of MEP opened the file and saved it? That should upgrade the proxies and then a current OE should work fine.You shouldn't even need to do that. As long as Helen has the OE's installed, she can directly open older/current versions of MEP drawings and have enabled objects.

But if she is only running AutoCAD 2008 with the enablers, and someone tried to save down an MEP 2010 drawing, that won't work, because the 2008 OE's cannot handle the 2010 MEP objects regardless of DWG file version.

[scott.wilcox]

You shouldn't even need to do that. As long as Helen has the OE's installed, she can directly open older/current versions of MEP drawings and have enabled objects.

But if she is only running AutoCAD 2008 with the enablers, and someone tried to save down an MEP 2010 drawing, that won't work, because the 2008 OE's cannot handle the 2010 MEP objects regardless of DWG file version.

Remember, SAVEAS to a previous version only applies to the AutoCAD objects, not the vertical objects, they only migrate upwards.

We recently switched to Civil 3D 2010, and I am reminding users to save a separate file, since some folks in other offices have not upgraded yet, and will not be able to open in a previous civil version.

[h.jobe]

Sorry it took me so long to respond.

Thanks! The MEP enabler took care of it.