Yes, you need to package the DLLs and OCXs and make sure they get properly
registered. I assume that all of your target machines already have Access
installed, so that won't be an issue. If so, any packaging product will
work.
If your target machines don't have Access already installed, you'll need to
look into getting the royalty-free Access runtime. You need to purchase the
following in order to create an Access 2003 runtime application:
- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)
The ADE is the product that gives you the license to deploy the 2003 runtime
components and you have to have Access 2003 installed in order to install
the ADE.
If you're using MSDN, note that while VSTO is available in all subscription
levels of MSDN, the Access Developer Extensions are not included with all
versions. ADE is only available at Universal level.
The stand-alone VSTO box includes both VSTO and the ADE.
See
http://msdn.microsoft.com/vstudio/office/officetools.aspx or
http://office.microsoft.com/en-us/assistance/HA011208861033.aspx for more
details
While VSTO includes a Packaging and Deployment Wizard, many people find it
to be somewhat lacking. One 3rd party product that gets a lot of good
reviews specifically for packaging Access runtime applications is the one
from SageKey
http://www.sagekey.com/