C
Chris
Hi
I have built an application in Access 2003 which I have succesfully packaged
up and deployed via the ADE Package Wizard (to include runtime). However I
have now come across a situation which I am not sure the Wizard manages
(unless I am doing something wrong) and wondered how best to move forward.
I now have cause to include an .OCX application which needs to be included
and registered as part of the deployment. The ADE Wizard allows me to include
the file, but does not register it.
Should it do so, or is this a limitation of ADE packaging?
I started looking at building a deployment solution in Visual Studio, but as
I am new to this I have some questions on it. It works in the sense that it
installs all the code and registers the ActiveX code, but:
a) How do I check that the target machine has the pre-req Windows build/SP
level etc that the ADE does?
b) I have included the Access.CAB and MSI into the build, but does this
install the Runtime environment, and if so, how can I check to see if Access
is already installed?
c) The runtime environment is flagged at not needing to be registered, is
this correct?
Any help greatfully received.
Regards
Chris
I have built an application in Access 2003 which I have succesfully packaged
up and deployed via the ADE Package Wizard (to include runtime). However I
have now come across a situation which I am not sure the Wizard manages
(unless I am doing something wrong) and wondered how best to move forward.
I now have cause to include an .OCX application which needs to be included
and registered as part of the deployment. The ADE Wizard allows me to include
the file, but does not register it.
Should it do so, or is this a limitation of ADE packaging?
I started looking at building a deployment solution in Visual Studio, but as
I am new to this I have some questions on it. It works in the sense that it
installs all the code and registers the ActiveX code, but:
a) How do I check that the target machine has the pre-req Windows build/SP
level etc that the ADE does?
b) I have included the Access.CAB and MSI into the build, but does this
install the Runtime environment, and if so, how can I check to see if Access
is already installed?
c) The runtime environment is flagged at not needing to be registered, is
this correct?
Any help greatfully received.
Regards
Chris