How do I package ActiveX controls using Access 2003 Developer Ext.

[Guest]

I am moving to Access 2003 and with the Access 2003 Developer Extensions,
there is not a way to package ActiveX controls that will register when
installed, which was available in XP Developer tools.

Is there a workaround to distribute the controls with the Access database

 

[Paul Overway]

You'll either have to use a different installer (which I recommend), or
create an installer for your activex components using something other than
PDW and then do a chained install for the package that contains your activex
components. There are other issues with PDW generated installers as well,
hence my suggestion that you find another installer...especially if you'll
be distributing to users outside your company. Many will suggest using
SageKey, but there is a white paper at site below that may be of help too.

 

[Albert D. Kallal]

An interesting side note:

While the a2003 Package wizard does not include abilities to install
activeX, the a2003 runtime does in fact install the supported the list of
activeX controls for ms-access.

in other words, the Calendar control, Treeview, listview, and a few others
are actually installed by default.

This means if you stick to the supported list of activeX controls, you in
fact never have to install them, they just work, and they don't break.

In fact, this feature change is so nice for the a2003 runtime, that it is
actually preferred over the full version, since anyone with the a2003
runtime will have the calendar control, and treeview installed. While I did
give up on the calendar control some years ago (wrote my own), the treeview
is now a practial contorl to use...and it gets installed by default....