AutoCAD 2008 and ObjectoARX

[jramos]

About 1 year ago I created a plugin to AutoCAD 2008 that used the COM to interface with ObjectARX (mainly I have a reference in my solution to "AutoCAD/ObjectDBX Common 17.0 Type Library") and it works great. But only for the 32-bit version of AutoCAD 2008.

Now I'm trying to recompile the solution but I can't find "AutoCAD/ObjectDBX Common 17.0 Type Library" in the list of COM references available. "AutoCAD 2008 Type Library" is available but I can't find "AutoCAD/ObjectDBX Common 17.0 Type Library" anywhere...

I've read some presentations about considerations to have when porting to AutoCAD 2008 64-bit, and everyone of them informs me that I can still use ObjectoARX. I simply can't figure out how...

Thanks

[Anonymous]

I've been stuck on this same problem for over a month. The file c:\program files\common files\autodesk shared\axdb17enu.tlb is where it's supposed to be, but when you try to select it from the References dialog box in the VBAIDE, it comes back as "MISSING".

Ben Rand
FLSmidth CEntry

[Anonymous]

Do you have a 64 bit system with both 32 and 64 bit versions of AutoCAD
installed? From what I've heard, that will foul things up.

On the COM tab in the references dialog, look for "AXDBLib".

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD
Supporting AutoCAD 2000 through 2010

http://www.acadxtabs.com

Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");

wrote in message news:6327850@discussion.autodesk.com...
About 1 year ago I created a plugin to AutoCAD 2008 that used the COM to
interface with ObjectARX (mainly I have a reference in my solution to
"AutoCAD/ObjectDBX Common 17.0 Type Library") and it works great. But only for
the 32-bit version of AutoCAD 2008.

Now I'm trying to recompile the solution but I can't find "AutoCAD/ObjectDBX
Common 17.0 Type Library" in the list of COM references available. "AutoCAD 2008
Type Library" is available but I can't find "AutoCAD/ObjectDBX Common 17.0 Type
Library" anywhere...

I've read some presentations about considerations to have when porting to
AutoCAD 2008 64-bit, and everyone of them informs me that I can still use
ObjectoARX. I simply can't figure out how...

Thanks

[Anonymous]

No, 64 bit Acad only on the 64 bit machine. I have code in place that automatically distributes centralized DVB files to our CAD users. Because the development of those files has always been on 32-bit systems, the references are setup accordingly. It looks like I'm going to have to save a "64-bit" version of the DVB file referencing AXDBLib and a 32-bit version for the rest.

And before anyone attacks me for talking about VBA in the .NET group...my apologies, I just found the thread and responded before I realized where this was.

Thanks for the quick reply, Tony. I'll post back if/when I get this to work.

Ben

[Anonymous]

I was asking the OP that because the issue affects VB.NET.

Don't know about VBA.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD
Supporting AutoCAD 2000 through 2010

http://www.acadxtabs.com

Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");

wrote in message news:6328285@discussion.autodesk.com...
No, 64 bit Acad only on the 64 bit machine. I have code in place that
automatically distributes centralized DVB files to our CAD users. Because the
development of those files has always been on 32-bit systems, the references are
setup accordingly. It looks like I'm going to have to save a "64-bit" version of
the DVB file referencing AXDBLib and a 32-bit version for the rest.

And before anyone attacks me for talking about VBA in the .NET group...my
apologies, I just found the thread and responded before I realized where this
was.

Thanks for the quick reply, Tony. I'll post back if/when I get this to work.

Ben

[jramos]

I'm running Windows 7 64-bit with only the 64-bit version of AutoCAD 2008 installed.
In the COM tab there is nothing named "AXDBLib"

[Anonymous]

Are you running as an administrator?

If not, one thing you can try is to right click on the
AutoCAD icon and choose 'Run As Administrator...",
and after that see if it has updated the registry.


--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD
Supporting AutoCAD 2000 through 2010

http://www.acadxtabs.com

Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");

wrote in message news:6328527@discussion.autodesk.com...
I'm running Windows 7 64-bit with only the 64-bit version of AutoCAD 2008
installed.
In the COM tab there is nothing named "AXDBLib"

[jramos]

I've tried that and it didn't work.
Out of desperation I tried to add almost every .ddl in the AutoCAD folder to the solution, but without success.

[Anonymous]

VBA Projects: I was able to get my project to work by going into the VBAIDE, selecting the project then Tools-->References and unchecking the Autocad/ObjectDBX Common 17.0 Type Library. Close the References dialog, then reopen it and select AXDBLib. Because we run mostly 32-bit Autocad (this 64-bit is a test box), I wound up having to have a "64-bit" version of my VBA project and a "32-bit" version.

There are a few properties that have to be updated in the "64-bit" version of the VBA project as well. ObjectID needs to be changed to ObjectID32, OwnerID to OwnerID32, ObjectIDToObject to ObjectIDToObject32.

Finally, only the last DVB file loaded in 64-bit Autocad registers properly for Autocad event notification (this was confirmed by ADN support). Our "main" project references a secondary library project and by default was loading main first, then the library project. None of the event handlers in the "main" project were going off when Autocad events were fired until I changed the load order. Fortunately only the "main" project had Autocad event handlers or I would have had to move some code.

Everyone has reemphasized the need to port the VBA projects to .NET as soon as possible.

Hope this is helpful,

Ben Rand

[Anonymous]

Great.

I hope you're not using the Sheet Set API.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD
Supporting AutoCAD 2000 through 2010

http://www.acadxtabs.com

Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");

wrote in message news:6329541@discussion.autodesk.com...
VBA Projects: I was able to get my project to work by going into the VBAIDE,
selecting the project then Tools-->References and unchecking the
Autocad/ObjectDBX Common 17.0 Type Library. Close the References dialog, then
reopen it and select AXDBLib. Because we run mostly 32-bit Autocad (this 64-bit
is a test box), I wound up having to have a "64-bit" version of my VBA project
and a "32-bit" version.

There are a few properties that have to be updated in the "64-bit" version of
the VBA project as well. ObjectID needs to be changed to ObjectID32, OwnerID to
OwnerID32, ObjectIDToObject to ObjectIDToObject32.

Finally, only the last DVB file loaded in 64-bit Autocad registers properly for
Autocad event notification (this was confirmed by ADN support). Our "main"
project references a secondary library project and by default was loading main
first, then the library project. None of the event handlers in the "main"
project were going off when Autocad events were fired until I changed the load
order. Fortunately only the "main" project had Autocad event handlers or I would
have had to move some code.

Everyone has reemphasized the need to port the VBA projects to .NET as soon as
possible.

Hope this is helpful,

Ben Rand

[jramos]

Well, for C# there is no such thing...
I've looked everywhere and I can't find any reference to the "Autocad/ObjectDBX Common 17.0 Type Library" or "AXDBLib"

I'm I the only person trying to use the COM interface in C# with a 64-bit installation of AutoCAD? As anyone actually managed to do this? Is it possible?

[Anonymous]

Hello Tony,
What's the problem with the Sheet Set API?
We have some developers here that are using it quite a bit with no problems.

Thanks,
Mike

> Great.
>
> I hope you're not using the Sheet Set API.
>
> AcadXTabs: MDI Document Tabs for AutoCAD
> Supporting AutoCAD 2000 through 2010
> http://www.acadxtabs.com
>
> Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");
>
> wrote in message news:6329541@discussion.autodesk.com...
> VBA Projects: I was able to get my project to work by going into the
> VBAIDE,
> selecting the project then Tools-->References and unchecking the
> Autocad/ObjectDBX Common 17.0 Type Library. Close the References
> dialog, then
> reopen it and select AXDBLib. Because we run mostly 32-bit Autocad
> (this 64-bit
> is a test box), I wound up having to have a "64-bit" version of my VBA
> project
> and a "32-bit" version.
> There are a few properties that have to be updated in the "64-bit"
> version of the VBA project as well. ObjectID needs to be changed to
> ObjectID32, OwnerID to OwnerID32, ObjectIDToObject to
> ObjectIDToObject32.
>
> Finally, only the last DVB file loaded in 64-bit Autocad registers
> properly for Autocad event notification (this was confirmed by ADN
> support). Our "main" project references a secondary library project
> and by default was loading main first, then the library project. None
> of the event handlers in the "main" project were going off when
> Autocad events were fired until I changed the load order. Fortunately
> only the "main" project had Autocad event handlers or I would have had
> to move some code.
>
> Everyone has reemphasized the need to port the VBA projects to .NET as
> soon as possible.
>
> Hope this is helpful,
>
> Ben Rand
>

[Anonymous]

You can't use the SheetSet API on 64 bit AutoCAD from VBA,
because some genius at Autodesk decided to not support an
IDispatch-based implementation, which is required for using it
from another process (VBA runs in a separate 32 bit process
on 64 but AutoCAD).

There's no problem using it from a VB.NET .dll, just VBA.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD
Supporting AutoCAD 2000 through 2010

http://www.acadxtabs.com

Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");

"Michael Robertson" wrote in message
news:6330182@discussion.autodesk.com...
Hello Tony,
What's the problem with the Sheet Set API?
We have some developers here that are using it quite a bit with no problems.

Thanks,
Mike

> Great.
>
> I hope you're not using the Sheet Set API.
>
> AcadXTabs: MDI Document Tabs for AutoCAD
> Supporting AutoCAD 2000 through 2010
> http://www.acadxtabs.com
>
> Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");
>
> wrote in message news:6329541@discussion.autodesk.com...
> VBA Projects: I was able to get my project to work by going into the
> VBAIDE,
> selecting the project then Tools-->References and unchecking the
> Autocad/ObjectDBX Common 17.0 Type Library. Close the References
> dialog, then
> reopen it and select AXDBLib. Because we run mostly 32-bit Autocad
> (this 64-bit
> is a test box), I wound up having to have a "64-bit" version of my VBA
> project
> and a "32-bit" version.
> There are a few properties that have to be updated in the "64-bit"
> version of the VBA project as well. ObjectID needs to be changed to
> ObjectID32, OwnerID to OwnerID32, ObjectIDToObject to
> ObjectIDToObject32.
>
> Finally, only the last DVB file loaded in 64-bit Autocad registers
> properly for Autocad event notification (this was confirmed by ADN
> support). Our "main" project references a secondary library project
> and by default was loading main first, then the library project. None
> of the event handlers in the "main" project were going off when
> Autocad events were fired until I changed the load order. Fortunately
> only the "main" project had Autocad event handlers or I would have had
> to move some code.
>
> Everyone has reemphasized the need to port the VBA projects to .NET as
> soon as possible.
>
> Hope this is helpful,
>
> Ben Rand
>

[Anonymous]

Hello Tony,
Thanks for the update, we are only doing .NET development.


> You can't use the SheetSet API on 64 bit AutoCAD from VBA,
> because some genius at Autodesk decided to not support an
> IDispatch-based implementation, which is required for using it
> from another process (VBA runs in a separate 32 bit process
> on 64 but AutoCAD).
> There's no problem using it from a VB.NET .dll, just VBA.
>
> AcadXTabs: MDI Document Tabs for AutoCAD
> Supporting AutoCAD 2000 through 2010
> http://www.acadxtabs.com
>
> Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");
>
> "Michael Robertson" wrote in
> message
> news:6330182@discussion.autodesk.com...
> Hello Tony,
> What's the problem with the Sheet Set API?
> We have some developers here that are using it quite a bit with no
> problems.
> Thanks,
> Mike
>> Great.
>>
>> I hope you're not using the Sheet Set API.
>>
>> AcadXTabs: MDI Document Tabs for AutoCAD
>> Supporting AutoCAD 2000 through 2010
>> http://www.acadxtabs.com
>> Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");
>>
>> wrote in message news:6329541@discussion.autodesk.com...
>> VBA Projects: I was able to get my project to work by going into the
>> VBAIDE,
>> selecting the project then Tools-->References and unchecking the
>> Autocad/ObjectDBX Common 17.0 Type Library. Close the References
>> dialog, then
>> reopen it and select AXDBLib. Because we run mostly 32-bit Autocad
>> (this 64-bit
>> is a test box), I wound up having to have a "64-bit" version of my
>> VBA
>> project
>> and a "32-bit" version.
>> There are a few properties that have to be updated in the "64-bit"
>> version of the VBA project as well. ObjectID needs to be changed to
>> ObjectID32, OwnerID to OwnerID32, ObjectIDToObject to
>> ObjectIDToObject32.
>> Finally, only the last DVB file loaded in 64-bit Autocad registers
>> properly for Autocad event notification (this was confirmed by ADN
>> support). Our "main" project references a secondary library project
>> and by default was loading main first, then the library project. None
>> of the event handlers in the "main" project were going off when
>> Autocad events were fired until I changed the load order. Fortunately
>> only the "main" project had Autocad event handlers or I would have
>> had to move some code.
>>
>> Everyone has reemphasized the need to port the VBA projects to .NET
>> as soon as possible.
>>
>> Hope this is helpful,
>>
>> Ben Rand
>>