"Tor" <ta*@FJERNDETTEconsipio.dk> wrote in message
news:43**********************@dread14.news.tele.dk ...
Where and how do I specify what components I want to include in my
installation package., and how do I make them register?
In the new package and deploy, there is no longer provisions for activeX
controls. You can either edit the resulting MSI with the oraca tools, but I
think a better approach would be to use a installer for those additional
active X contorls.
Do note that ms-access officially only supports the 6 basic activeX controls
(can, listview, treeview) etc. And, do note that the a2003 wizard includes
these six controls. So, for things like the calendar etc, a copy is already
included by default.
If your cal is a custom one, then you will have to provide some code that
registers the controls. I would suggest you use the free "inno" installer do
this.
You will notice that 2003 been out for about 2+ years, and you never see
anyone complain about the lack of activeX install stuff with the p & d, and
reason is of course most of us stopped using 3rd party activeX controls due
to reference problems....
So, if you stick to 6 active controls that ms-access supports (listview,
treeview, calender etc), then you will NOT have any problems, as those
controls are installed, and registered by default.
For any other ones, you will have to edit the MSI file that the p&d
produces, or even better us wrap the runtime install + your activeX install
in Inno. You can find Inno here
http://www.jrsoftware.org/isinfo.php
I build my package with the a2003 runtime, but then use Inno to deploy
it....
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com http://www.members.shaw.ca/AlbertKallal 
