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
>>