Dependency Module: MDAC 2.81 SP1

[Adam]

Dependency Module: MDAC 2.81
Last Revision: June 17, 2005 (002)

Overview
Use the MDAC 2.81 SP1 dependency module with Setup Factory 7.0 to detect and install Microsoft Data Access Components version 2.81. The core components of MDAC are ADO, OLE DB, and ODBC.

Background Information
Microsoft Data Access Components (MDAC) is a set of software components that are used to provide applications a means to access data from various data storage sources, with a focus on access to Microsoft SQL Server. A large number of applications, and the operating system itself, depend on MDAC-contained components for proper operation. MDAC is not a single product; rather, it is a collection of DLLs and associated component resources to support a number of different APIs, including Open Database Connectivity (ODBC), OLE DB, Microsoft ActiveX Data Objects (ADO), and Microsoft Remote Data Service (RDS). MDAC installation not only places a large number of common shared files in various places across the Microsoft Windows system drive, MDAC is also responsible for adding many keys to the registry.

Installation Instructions
To make the MDAC 2.81 dependency module available in your Setup Factory 7.0 projects, follow the steps below:

1. Close Setup Factory 7.0, if it is running.
2. Browse to the folder where Setup Factory 7.0 is installed on your system. By default it is C:\Program Files\Setup Factory 7.0.
3. Open the folder called Dependencies.
4. Unzip the contents of mdac28sp1.zip (see bottom of article) into the dependencies folder.
5. Create a subfolder of Dependencies and name it mdac28sp1.
6. Download the MDAC 2.81 installation file (MDAC_TYP.EXE) into the mdac28 subfolder.
7. Restart Setup Factory 7.0.

To use your new dependency module, select Resources > Dependencies from the main menu and click the Add button. MDAC 2.8sp1 should now be visible in the list of available modules.

Information Links

• Microsoft Knowledge Base Article 899456: Release Manifest for MDAC 2.81 (2.81.1117.6)
• MSDN Article: Microsoft Data Access Components (MDAC) Installation
  
• MSDN Downloads: SQL Server, MDAC, Access, Jet
  
• MSDN: Data Access and Storage Developer Center

Module Name: Microsoft MDAC 2.81
Type: Setup Factory 7.0 Dependency Module
Created By: Indigo Rose Software (6/17/2005)
Last Revision: June 20, 2005 (002)

[VeryXp]

Hi,

I just want to leave a note. I don't know if I'm right?

I've checked this article at Microsoft which talks about Installing MDAC 2.81 SP1 and I found it saying about installing MDAC 2.81 SP1 on Windows XP that it is "Installed with Windows XP SP2, otherwise cannot be installed". But when I checked the script which is responsible of installing MDAC 2.81 SP1, I saw it saying:
"-- Only install MDAC 2.81 if:
-- The version number is less than the MDAC 2.8 version "2.81" or not found.
-- The OS is NOT Windows 2003 or Windows 95"

Also here, I found this note : "Note The MDAC 2.8 SP1 stand-alone release is not supported on the Microsoft Windows XP operating system or on the Microsoft Windows Server 2003 operating system. To update the MDAC version that is installed together with Windows XP or with Windows Server 2003, you must use operating system service packs or Windows Update."
((???))

I also saw a note that warns about installing MDAC 2.81 SP1 where MS SQL Server 7.0 clustered nodes is preinstalled. again a warning says: "Do not install MDAC 2.6 or later versions on any Microsoft SQL Server 7.0 clustered nodes. If you install MDAC 2.6 or later versions on any node in the cluster, directly or through the installation of another program, it may cause a failure of the SQL Server Agent or other SQL Server services."

[aniketb78]

I am running Windows XP SP2. I added this dependency module to my installation and found that when it tries to run the detection code it drops into the case where it tries to install the MDAC. This however, causes an error as Windows will not allow MDAC 2.8 SP1 to install. It throws up the error message "This setup does not support installing on this operating system."

In order to fix this I reccomend changing the detection checking code from

if ((strOSName ~= "Windows Server 2003") and (strOSName ~= "Windows 95")) then

to the following

if ((strOSName ~= "Windows Server 2003") and (strOSName ~= "Windows 95") and (strOSName ~= "Windows XP")) then


This will ensure that Windows XP Users do not have a problem during the installation. Hope this helps anyone having this problem.

[bc2m]

Many thanks for the prompt response. Much appreciated!
Barry

[baransudtm]

Thenks Güzel Program

[baransudtm]

Bu Nİye Olmuyor Ya