Prash Shirolkar

May 2000

Summary: This document provides in-depth information on the Microsoft Data Access Components (MDAC) 2.5 redistribution stack, as well as the effect of Windows File Protection on its files on a computer running Microsoft® Windows® 2000 or Microsoft Windows Millennium—including information about what you can do to restore a damaged installation on Windows 2000 or Windows Millennium. This document also provides a breakdown of the MDAC 2.5 redistribution stack into its individual components and then addresses the characteristics of each technology. (12 printed pages)

Note   Even though a breakdown of the MDAC stack is provided, an all or nothing policy with regards to MDAC 2.5 redistribution is strongly recommended. Please refer to the End User License Agreement (in Mdaceula.txt) for details about redistributing MDAC 2.5. Additionally, from here on, the MDAC 2.5 redistribution stack will be referred to as the MDAC 2.5 stack. Finally, Windows File Protection (WFP) was initially referred to as System File Protection (SFP), hence any reference to WFP implies SFP as well.

Contents

Introduction
Windows File Protection and MDAC 2.5
The MDAC 2.5 Stack and Its Components
ADO
ODBC
OLE DB
SQL Server
Oracle
Microsoft Jet
RDS
Visual Fox Pro
References

Introduction

The MDAC 2.5 stack can be broadly categorized into the ActiveX Data Objects (ADO), OLE DB, Open Database Connectivity (ODBC), Remote Data Services (RDS), Microsoft Jet, and Microsoft Visual FoxPro® components. These components are highly dependent on one another. For example, ADO components are nonfunctional without the ODBC core, OLE DB core, and the back-end database's OLE DB provider or ODBC driver.

Windows File Protection and MDAC 2.5

A persistent issue in the history of the Windows operating systems is the ability of installation programs not affiliated with the operating system to overwrite shared system files. After such installations, the user often experiences unpredictable system performance, ranging from application errors to operating system crashes. This problem affects several types of files, most commonly dynamic-link libraries (DLLs) and executable files (EXEs), and is often referred to as "DLL Hell." (For more details, see The End of DLL Hell, listed in the References section.)

Windows 2000 has a new feature called Windows File Protection (WFP) that prevents the replacement, by installations other than operating system updates, of system files that ship with Windows 2000. By preventing the replacement of essential system files, file version mismatches can now be avoided.

What MDAC files are covered by WFP?

All the MDAC files protected by WFP are listed in the tables in the individual MDAC technology sections of this document. A "1" in the WFP column signifies it is protected by WFP, and a "0" indicates that it is not.

How can a damaged installation of the MDAC 2.5 files on Windows 2000 be repaired without reinstalling the operating system?

Windows 2000 ships with MDAC 2.5. WFP will protect many of the MDAC 2.5 DLLs from being changed. In the rare event that a MDAC 2.5 WFP DLL is corrupted, contact Microsoft Product Support Services for instructions. A corrupted non-WFP file can be overwritten by copying the correct file from the MDAC 2.5 stack.

The MDAC 2.5 Stack and Its Components

The remaining sections of this document delve into each of the MDAC technologies, and each section includes a table that provides the following information:

• All file names contained in the given component
• Whether each file is under Windows File Protection (0 = no, 1 = yes)
• The component release version in which the file is found
• A brief description of the file
• The file's location

The location column abbreviations are explained in the following table.

Additionally, some of the components provide their own HTML Help files in \HELP folder.

ADO

ADO is the flagship application programming interface (API) for Universal Data Access (UDA). ADO 2.5 provides new objects, the Record object and the Stream object, that can retrieve data from URLs through the Microsoft OLE DB Provider for Internet Publishing (MSDAIPP). Additionally, traditional ADO objects such as the Connection and Recordset objects, as well as the new ones, can bind directly to a URL and retrieve data. ADO 2.5 also provides support for semi-structured data (also referred to as ragged or nonrectangular data).

In MDAC 2.5, ADO includes the ADOX and ADO MD subcomponents. Apart from the ADO object model, the ADO core components include the resource and rowset helper libraries, as well as the ADO 2.0 and 2.1 type libraries. ADO MD, the high-level object model for exposing multidimensional data, is contained in one DLL (msadomd.dll), as is ADOX (msadox.dll). The ActiveX Data Objects 2.1 Type Library is a new addition MDAC 2.5.

The MDAC 2.5 ADO Stack

ODBC

ODBC is still a widely accepted API for database access. It is based on the Call-Level Interface (CLI) specifications from X/Open and ISO/IEC for database APIs and uses Structured Query Language (SQL) as its database access language. It provides the client a unified means, with the same source code, of accessing relational data from different database management systems.

In addition to the thunking DLLs, the ODBC components include the all-important ODBC Driver Manager, the Windows 2000 Component Services (or MTS, if you are using Microsoft Windows NT®) connection pooling manager, the driver manager trace DLL, and the ODBC cursor library. Other components include the ODBC resources file, the installer DLL, and the Driver Configuration program files.

The ODBC Administrator still forms an integral part of the ODBC core, and another file of note is the ODBC HTML Help file that is installed in the \WIN folder.

The MDAC 2.5 ODBC Stack

OLE DB

OLE DB offers a set of COM interfaces that you can use to access both relational and nonrelational data. OLE DB 2.5 introduced a new set of interfaces designed to incorporate the semi-structured data model. This effectively added support for hierarchical data stores, nonrectangular result sets, and for binding directly to objects through URLs. Some examples of hierarchical stores are file stores and message stores, and examples of nonrectangular data include simple or complex documents, e-mails, and so forth. Support for this kind of access is provided through the OLE DB row and stream objects, direct binding, and scoped operation capability.

Except for the new interfaces, the objects that form the OLE DB core are generally the same. A prominent new addition, however, is the root binder object, which provides a mechanism to directly bind to URLs and retrieve nonrectangular data. Other new features include OLE DB 2.5 runtime routines and OLE DB JavaScript and VBScript include files.

The MDAC 2.5 OLE DB Stack

SQL Server

The list of SQL Server subcomponents has no changes from the MDAC 2.1 version. These subcomponents are associated with the SQL Server ODBC Driver and OLE DB Provider for SQL Server. Again, the breakdown here is based on products rather than dependencies. Therefore, the network libraries are listed under SQL Server OLE DB even though the SQL Server ODBC Driver is dependent on them. Other important subcomponents include the code page translators, the client-configuration utility, SQL enterprise components, and the SQL Server Catalog update.

The MDAC 2.5 SQL Server ODBC and OLE DB Stack

Oracle

In MDAC 2.5, the Oracle components, including the Oracle Call Interface (OCI) DLL and the code page translator, are unchanged for the Oracle ODBC Driver and the OLE DB Provider for Oracle.

The MDAC 2.5 Oracle ODBC and OLE DB Stack

Microsoft Jet

Microsoft Jet has 28 subcomponents in the MDAC 2.5 stack. Generally, the list is unchanged except for the HTML Help file. The Jet components include the Jet Engine with its numerous ISAMs, the Reconciler library, the Replication library, the Sort library, Expression Service binaries, the Jet ODBC Driver, the OLE DB Provider for Microsoft Jet, and the Microsoft Jet and Replication (JRO) objects.

The MDAC 2.5 Microsoft Jet Stack

RDS

In MDAC 2.5, the list of RDS subcomponents is unchanged from MDAC 2.1. The stack includes the following components and associated resources: the RDSServer.DataFactory object and its handler, the RDS.DataControl object, the RDS ISAPI library, the Data Shaping Service for OLE DB, the OLE DB Persistence Provider, the OLE DB Remoting Provider, and the OLE DB Cursor Service for OLE DB.

The MDAC 2.5 RDS Stack

Visual FoxPro

The Visual FoxPro components include the Visual FoxPro ODBC driver and its corresponding help file.

The MDAC 2.5 Visual FoxPro Stack

References

Redistributing Microsoft Data Access

Universal Data Access Web Page

OLE DB Programmer's Reference

The End of DLL Hell

MSDN Online Help - Microsoft Data Access Components