Article ID: 2784916 - View products that this article applies to.
Microsoft Access 2010 Runtime is a technology that can be a prerequisite for custom applications. Although this technology can be specified as a prerequisite, it is not included in Microsoft Visual Studio 2008.
In most cases, you should implement and test such prerequisites for custom applications. This includes Bootstrapper Manifest Generator.
Note Bootstrapper Manifest Generator is an archived tool for working with prerequisite bootstrapping applications in Visual Studio. This tool is not included in Visual Studio 2008, and is not supported by Microsoft. Microsoft Support does not have the information that you need to fully populate the Bootstrapper Manifest Generator XML files. Microsoft only provides guidance in creating the custom bootstrappers.
To help determine which prerequisites are required, you can use the MSI APIs instead of using Bootstrapper Manifest Generator.
When you set the Access 2010 Runtime as a prerequisite, the Setup.exe file that is provided in the Access 2010 Runtime download must be included so that the user can accept the Microsoft Software License Terms. This applies whether the installation is part of the prerequisites, or is a stand-alone installation.
To obtain Access 2010 Runtime, go to the following Microsoft website:
Access 2010 Runtime downloadTo obtain Microsoft Access Database Engine 2010 Redistributable, go to the following Microsoft website:
Microsoft Access Database Engine 2010 Redistributable downloadFor more information about Access 2010 Runtime Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2460015For more information about how to create a product manifest file, go to the following MSDN website:
(http://support.microsoft.com/kb/2460015/ )Description of Access 2010 Runtime Service Pack 1
How to create a product manifest fileFor more information about MSI APIs, go to the following MSDN website:
Installer function reference for Windows
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2784916 - Last Review: December 20, 2012 - Revision: 1.0