(c) 1999 Microsoft Corporation. All rights reserved.
This document provides late-breaking or other information that supplements the Microsoft Data Access Components (MDAC) documentation.
Contents
1. MDAC TECHNICAL NOTES
2. MDAC KNOWN BUGS, LIMITATIONS, AND WORKAROUNDS
3. MDAC FILELIST AND FILE INFORMATION
------------------------
1. MDAC TECHNICAL NOTES
------------------------
MDAC Release Notes
This file, MDACReadme.txt, contains technical notes, information on bugs and workarounds, and information too late to include in the documentation for the Microsoft Data Access Components.
The release notes for each of the Microsoft Data Access Components can be found in the following locations:
2.1 When using ADSI 2.0 with MDAC 2.1, ADSI will disable its ADO functionality. Other features of ADSI will continue to work. MDAC 2.1 does not affect accessing ADSI via ADSI Interfaces.
For example, opening an ADO Connection object in ADSI will fail when MDAC 2.1 is installed.
Con.Provider = "ADsDSOObject"
Con.Open "Active Directory Srv Interface" <= This line fails
ADSI will be posting a resolution to this problem on http://www.microsoft.com/adsi
2.2 On Windows 95, if you install MDAC from a UNC, you receive an error. This error does not occur if you map a drive instead of using the UNC, even if the drive is not persistent.
2.3 If you install MDAC 2.1 on a computer running applications that access SQL Server 6.5 through the OLE DB Provider for SQL Server or the SQL Server ODBC Driver, and if the catalog stored procedures installed on that SQL Server 6.5 are not current, the provider or driver will generate the following warning message:
OLE DB Provider for SQL Server:
The catalog stored procedures installed on server <server_name> are version <version#>; version <version#> or later is required to support IDBSchemaRowset. Please contact your system administrator.
SQL Server ODBC Driver:
The ODBC catalog stored procedures installed on server <server_name> are version <version#>; version <version#> or later is required to ensure proper operation. Please contact your system administrator.
If an application ignores this message, it may experience some problems (such as loss of schema information).
To correct this:
* You must install instcat.sql that comes with MDAC 2.1 on the 6.5 server
- or -
* Install SQL Server 6.5 SP5 on the server. Installing SQL Server 6.5 SP5 automatically runs instcat.sql.
2.4
MDAC 2.1 sp2 now supports installation on Windows NT 4.0 Terminal Server. To install, you must have Administrator privileges and you must set the mode to INSTALL. Run mdac_typ.exe as normal. Then run mdac.cmd from the winnt\system32 directory and reboot.
Note: You may need to run additional scripts included with Terminal Server to complete the install.
This section lists the files installed by Microsoft Data Access Components 2.1 SP2 Setup. It contains information on file versions, descriptions, and install locations.
Component
Filename Version Install Location Description
ADO
MDAC21RD.txt None. \[programfiles]\[commonfiles]\System\ADO Release Notes for MDAC21
adoapt15.reg None. \[programfiles]\[commonfiles]\System\ADO Apartment Thread Model batch file
adofre15.reg None. \[programfiles]\[commonfiles]\System\ADO Free Thread Model batch file
adojavas.inc None. \[programfiles]\[commonfiles]\System\ADO JavaScript Include file for ADO
adoreadm.txt None. \[programfiles]\[commonfiles]\System\ADO Release Notes for ADO
adovbs.inc None. \[programfiles]\[commonfiles]\System\ADO VBScript Include file for ADO
makapt15.bat None. \[programfiles]\[commonfiles]\System\ADO Apartment Thread Model batch file
makfre15.bat None. \[programfiles]\[commonfiles]\System\ADO Free Thread Model batch file
