AEC Objects Alert

[pixelarch]

We using CODEBOOK to generate the layout plan, elevation. When we insert form CODEBOOK this alert appear.

Last time, we work with ACAD 2011 normally. Got the problem when upgrade to 2013.

Please see the attached and advice. Thanks.

[pixelarch]

We using CODEBOOK to generate the layout plan, elevation. When we insert form CODEBOOK this alert appear.

Last time, we work with ACAD 2011 normally. Got the problem when upgrade to 2013.

Please see the attached and advice. Thanks.

[Alfred.NESWADBA]

Hi,

>> Last time, we work with ACAD 2011 normally. Got the problem when upgrade to 2013.

And where does the message come from? It says AutoCAD 2012 in it's title!

>> When we insert form CODEBOOK this alert appear

I don't know this app, so what exactly are you inserting? If it's a drawing (to get a block into your current project) you should first update these external drawings (so they get updated with their AEC-objects), then you can insert them without issues.

If it's not a drawing that you insert, then let us know what you mean by "insert form CODEBOOK".

- alfred -

[Alfred.NESWADBA]

Hi,

>> Last time, we work with ACAD 2011 normally. Got the problem when upgrade to 2013.

And where does the message come from? It says AutoCAD 2012 in it's title!

>> When we insert form CODEBOOK this alert appear

I don't know this app, so what exactly are you inserting? If it's a drawing (to get a block into your current project) you should first update these external drawings (so they get updated with their AEC-objects), then you can insert them without issues.

If it's not a drawing that you insert, then let us know what you mean by "insert form CODEBOOK".

- alfred -

[pendean]

that pop-up message is trying to inform you of the following (very common):
SOMEONE OPENED AND SAVED YOUR FILE IN R2013 OR R2014. What this did was upgrade your AEC content and you now have a mix and a mess because 2013 and higher will upgrade and remove AEC contentn from editing access to for lower versions. REGARDLESS OF WHAT YOU SET SAVE TO DO IN 2013/2014.

It's a reality anyone that uses vertical versions of autocad is painfully aware of sadly. Nothing you can do about it except to limit versions of autocad touching your files within a project, or upgrade everyone to 2013. Your choice. No fix or workaround, sorry.

[pendean]

that pop-up message is trying to inform you of the following (very common):
SOMEONE OPENED AND SAVED YOUR FILE IN R2013 OR R2014. What this did was upgrade your AEC content and you now have a mix and a mess because 2013 and higher will upgrade and remove AEC contentn from editing access to for lower versions. REGARDLESS OF WHAT YOU SET SAVE TO DO IN 2013/2014.

It's a reality anyone that uses vertical versions of autocad is painfully aware of sadly. Nothing you can do about it except to limit versions of autocad touching your files within a project, or upgrade everyone to 2013. Your choice. No fix or workaround, sorry.

[pixelarch]

How can we prevent this dislog appear?

[pixelarch]

How can we prevent this dislog appear?

[Jay_B]

Your post is a bit confusing.
You stated "we work with ACAD 2011 normally. Got the problem when upgrade to 2013."
But the caption you provided says 2012 on it?
I'm not at all familiar with Codebook but as has been mentioned AEC objects aren't generally backward compatible.
So if it works as other AutoCad verticals it's likely forward compatible but not backwards.
If someone opens a file in 2013, saves the file and then opens it in an older version such as 2012 or 2011 it could be causing the dialog your getting.

[Jay_B]

Your post is a bit confusing.
You stated "we work with ACAD 2011 normally. Got the problem when upgrade to 2013."
But the caption you provided says 2012 on it?
I'm not at all familiar with Codebook but as has been mentioned AEC objects aren't generally backward compatible.
So if it works as other AutoCad verticals it's likely forward compatible but not backwards.
If someone opens a file in 2013, saves the file and then opens it in an older version such as 2012 or 2011 it could be causing the dialog your getting.

[pendean]

turn off PROXYNOTICE if all you want to do is hide the problem you've created instead of stopping it from happening.
There might also be a "do not show this again' box on the pop-up, use that too.
Good luck.

[pendean]

turn off PROXYNOTICE if all you want to do is hide the problem you've created instead of stopping it from happening.
There might also be a "do not show this again' box on the pop-up, use that too.
Good luck.

[pixelarch]

It just work with Proxy notice not AEC Objects alert.

[pixelarch]

It just work with Proxy notice not AEC Objects alert.

[pendean]

Then no 😞

[pendean]

Then no 😞

[dbroad]

The best way to prevent the dialog from appearing is for the whole project team to acknowledge the requirements of AutoCAD Architecture and similar verticals.  If any single project member is using an AEC/MEP application then the dwg format must be saved in the native format for that AEC/MEP application (if 2013, then 2013 drawing format, if 2012, then 2010-2012 format, etc).  AEC/MEP bring a lot of advantages in production over AutoCAD alone but will cause lots of frustration if the whole team is not using the same AutoCAD version and saving to the latest format that ALL members have.  You cannot save an AEC/MEP version back so that someone else can use the AEC objects in the earlier application version.

[dbroad]

The best way to prevent the dialog from appearing is for the whole project team to acknowledge the requirements of AutoCAD Architecture and similar verticals.  If any single project member is using an AEC/MEP application then the dwg format must be saved in the native format for that AEC/MEP application (if 2013, then 2013 drawing format, if 2012, then 2010-2012 format, etc).  AEC/MEP bring a lot of advantages in production over AutoCAD alone but will cause lots of frustration if the whole team is not using the same AutoCAD version and saving to the latest format that ALL members have.  You cannot save an AEC/MEP version back so that someone else can use the AEC objects in the earlier application version.

[pixelarch · Accepted solution]

This is the solution from our team :

"Thanks for your support. After several testing with CAD and Codebook, I have an experience to sort this error out. That is we create a new template drawing (.DWT)  from CAD 12 and delete the old template for CAD 13, change folder path. It works ok now.

We must remove CAD 11 and CAD 13 out of our machine if we want Codebook V11 to work correctly. If not, the error like this will happen again."

[pixelarch · Accepted solution]

This is the solution from our team :

"Thanks for your support. After several testing with CAD and Codebook, I have an experience to sort this error out. That is we create a new template drawing (.DWT)  from CAD 12 and delete the old template for CAD 13, change folder path. It works ok now.

We must remove CAD 11 and CAD 13 out of our machine if we want Codebook V11 to work correctly. If not, the error like this will happen again."

[Anonymous]

If you are using an autodesk AEC aplicattion, you need to install Object Enablers.

http://usa.autodesk.com/adsk/servlet/index?linkID=9240618&id=2753223&siteID=123112

[Anonymous]

If you are using an autodesk AEC aplicattion, you need to install Object Enablers.

http://usa.autodesk.com/adsk/servlet/index?linkID=9240618&id=2753223&siteID=123112