Bobby,
1. The ADT type libraries all start with AEC, but cover different parts of
the package. When I do an app, I usually just "blindly" grab everything that
starts with AEC. This way I have access to all the different objects.
2. The type libraries are forward compatible, i.e., if you select libraries
from 2i they will work in 3.0 and 3.3. However, the 2.0 libraries aren't a
complete as 3.3. If you select libraries in 3, the macros won't run in 2 (as
Rob can tell you). If I were you, I would developer the new routines in 3.3,
and not allow them on older versions of ADT. This way you have the
"AddCustomObject" support to add walls, doors, windows and the like, and in
3.3 you have access to the property set definitions. The 2.0 libraries are
pretty limiting. Once the type library is set with the macro, nothing has to
be done on the other machines to get it to run.
3. Relax and have fun!
Cheers,
Peter Funk
API Product Manager
Building Industry Division
Autodesk, Inc.
"Bobby Jones" wrote in message
news:1F072781AE08E7DDFDFE8FD5DC12B495@in.WebX.maYIadrTaRb...
> OK, as promised, I'm using VBA to complete my next project. I currently
> have ADT 2i and 3.0 on my machine but all others in the company are still
> on 2i, soon to be upgrading to 3.3. The question is, when setting my
> references in 2i, do I just blindly go about selecting everything that
> starts with AEC except for items that have 3.0 in them? Will my computer
> spontaneously combust if I reference a 3.0 ActiveX server with 2i? Will
the
> proper references be automatically set when someone else in the company
uses
> my radical new VBA app on their machine? Am I the only one that was this
> overwhelmed with their first VBA routine when making the switch-over?
> Mommy!!
> --
> Bobby C. Jones
>
>
>