Status: Unverified
GOAL:
Does the MERANT Driver support 'Distributed Transactions'
GOAL:
Does Merant ODBC driver support MTS/DTC (Microsoft Transaction Server - Distributed Transaction Coordinator):
FIX:
The Merant ODBC driver does not support Distributed transactions.
A list of databases that support MTS/DTC (Microsoft Transaction Server - Distributed Transaction Coordinator):
READ.ME
MERANT DataDirect Connect ODBC
Microsoft Windows 9x and Microsoft Windows NT
Version 3.60
December 1999
NOTE: You may only use DataDirect Connect ODBC with the platform(s) you have licensed. Licensing options are Windows 9x or Windows NT. The packing slip indicates your licensed platform(s).
This README file contains database driver information not included in the CONNECT ODBC REFERENCE or the online help.
CONTENTS
Version 3.60 Changes
Available DataDirect Connect ODBC Drivers
Driver Options
Notes and Known Problems
Installing and Using the Online Documents
Installed Files
Version 3.60 Changes
DB2 UDB
* Name changed from DB2 to DB2 UDB.
* The DB2 UDB driver is described in the CONNECT ODBC REFERENCE SUPPLEMENT.
Do NOT refer to the DB2 chapter in the CONNECT ODBC REFERENCE. The driver
described in that chapter is not currently shipping.
Informix
* New driver which supports both Informix 7 and Informix 9 via
INFORMIX-Connect 2.x.
* Supports MTS-DTC (Microsoft Transaction Server - Distributed Transaction
Coordinator).
Oracle
* Supports parameter arrays
* New option to allow static cursors with long data
* New option to limit schema for SQLProcedures to current user
* Support for {fn Convert (SQL_FLOAT)}
Oracle8
* Supports Oracle 7 servers
* Supports parameter arrays
* Supports asynchronous execution
* Supports Oracle 8.1.5 servers
* Supports LOBs as output parameters
* New option to allow static cursors with long data
* New option to limit schema for SQLProcedures to current user
* New option to optimize performance for long data
* Support for {fn Convert (SQL_FLOAT)}
* Enhanced DTC support
Sybase
* Supports HA (High Availability) via OpenClient 12.0
* Support MTS-DTC (Microsoft Transaction Server - Distributed Transaction
Coordinator) via OpenClient 12.0
* Supports ANSI Outer Join syntax when connected to a Sybase ASE 12.0
server
Sybase ASE
* New driver based on TDS wire protocol. Does not require ct-lib.
SQL Server
* New setup dialog.
XML
* New driver for XML data.
Available DataDirect Connect ODBC Drivers
Driver Supports
------ --------
Btrieve (IVBTR15.DLL) Btrieve 6.x, Pervasive.SQL 7.0, and
Pervasive.SQL 2000
dBASE (IVDBF15.DLL) dBASE III, IV, V files; Clipper files; FoxPro
2.5, 2.6, 3.0, and 6.0 (limited to FoxPro 3.0
functionality) files
DB2 UDB (IVUDB15.DLL) DB2 for UDB on OS/2, Windows NT, DB2/6000
Excel Workbook (IVXLWB15.DLL) Excel version 5 or 7 workbooks.
FoxPro 3.0 DBC FoxPro 3.0 DBC and FoxPro 6.0 DBC (limited to 3.0
DBC functionality) files
NOTE: The FoxPro 3.0 driver
functionality is built into the dBASE
driver.
Informix (IVINF15.DLL) Informix 7.x or 9.x via INFORMIX-Connect 2.x
OpenIngres (IVOING15.DLL) CA-OpenIngres 1.2 via Ingres Net 1.2
OpenIngres 2.0 (IVOI215.DLL) CA-OpenIngres 1.2 or 2.0 via Ingres Net 2.0
Oracle (IVOR715.DLL) Oracle 7.x or 8.x servers via SQL*Net 7.x
Oracle8 (IVOR815.DLL) Oracle servers 7.3.4 or higher via Net8 8.0.4 or
higher
Paradox (IVIDP15.DLL) Paradox 4, 5, 7, 8, and 9 tables
PROGRESS (IVPRO15.DLL) PROGRESS 7.3 and 8.x
SQLBase (IVGUP15.DLL) Centura Software SQLBase 6.5, 7.0, 7.5
SQL Server (IVMSSS15.DLL) Microsoft SQL Server 6.5 and 7.0
SQL Serv.er 6 (IVSS615.DLL) Microsoft SQL Server 6.5
Sybase (IVSYB15.DLL) System 10 and System 11 from Sybase,
Adaptive Server 11.x and 12.0 from
Sybase,
Sybase 4.92
Sybase ASE (IVASE15.DLL) Adaptive Server 11.x and 12.0 from
Sybase via
TDS wire protocol.
Text (IVTXT15.DLL) ASCII text files
XML (IVXML15.DLL) XML data
Driver Options
DataDirect has included non-standard options for the drivers that enable you to take full advantage of packaged ODBC-enabled applications requiring non-standard or extended behavior.
note: These options are not available for use with the SQL Server
driver.
To use these options, we recommend that you create a separate data source for each application. Using the registry editor (REGEDIT on Windows 9x and Windows NT 4.0, and REGEDT32 on Windows NT 3.5x), open the ODBC.INI section in the registry. In the section for the data source you created, add the string value WorkArounds (or WorkArounds2) with a value of n (for example, WorkArounds=n). The value n is the cumulative value of all options added together.
Note that each of these options has potential side effects related to its use. An option should only be used to address the specific problem for which it was designed. For example, WorkArounds=2 causes the driver to report that database qualifiers are not supported, even when they are. As a result, applications that use qualifiers may not perform properly when this option is enabled.
WorkArounds=1. If an ODBC driver reports that its
SQL_CURSOR_COMMIT_BEHAVIOR or SQL_CURSOR_ROLLBACK_BEHAVIOR is 0, then return 1 instead and force statements to be prepared again by the driver.
WorkArounds=2. Some applications cannot handle database qualifiers. If this option is on, the driver reports that qualifiers are not supported.
WorkArounds=4. Some applications require two connections to a database system. Since some database systems support only one connection, the second connection attempt fails. Turning this option on causes our drivers to detect this condition and have the two ODBC connections share a single physical connection to the database system.
WorkArounds=8. If an ODBC driver cannot deduce the number of rows affected by an INSERT, UPDATE, or DELETE, it may return -1 in SQLRowCount. Some products cannot handle this. Turning this option on causes the driver to return 1 instead.
WorkArounds=16. For SQLStatistics, if an ODBC driver reports an INDEX_QUALIFIER that contains a period, some applications raise a "tablename is not a valid name" error. Turning this option on causes the driver to return no INDEX_QUALIFIER.
WorkArounds=32. Turning this option on enables users of flat-file drivers to abort a long-running query by pressing the ESC key.
WorkArounds=64. This option results in a column name of C<position> where <position> is the ordinal position in the result set. For example, "SELECT col1, col2+col3 FROM table1" produces the column names "col1" and C2. SQLColAttributes/SQL_COLUMN_NAME returns <empty string> for result columns that are expressions. Use this option for applications that cannot handle <empty string> column names.
WorkArounds=256. Forces SQLGetInfo/SQL_ACTIVE_CONNECTIONS to be returned as 1.
WorkArounds=513. To prevent ROWID results, this option forces the SQLSpecialColumns function to return a unique index as returned from SQLStatistics.
WorkArounds=2048. Microsoft Access performs more efficiently when the output connection string of SQLDriverConnect returns DATABASE= instead of DB= for some data sources. This option forces DATABASE= to be returned.
WorkArounds=65536. This option strips trailing zeros from decimal results, which prevents Microsoft Access from issuing an error when decimal columns containing trailing zeros are included in the unique. index.
WorkArounds=131072. This option turns all occurrences of the double quote character ("") into the grave character (`). Some applications always quote identifiers with double quotes. Double quoting causes problems for data sources that do not return SQLGetInfo/SQL_IDENTIFIER_QUOTE_CHAR = <double quote>.
WorkArounds=524288. The Microsoft Foundation Classes (MFC) bind all
SQL_DECIMAL parameters with a fixed precision and scale, which causes truncation errors. Set this option to force the maximum precision/scalesettings.
WorkArounds=1048576. Some applications incorrectly specify a precision of 0 for character types when the value will be SQL_NULL_DATA. This option overrides the specified precision and sets the precision to 256.
WorkArounds=2097152. Some applications incorrectly specify a precision of -1 for character types. This option overrides the specified precision and sets the precision to 2000.
WorkArounds=4194304. For PowerBuilder users, this option converts all catalog function arguments to upper case unless they are quoted.
WorkArounds=536870912. This option allows for re-binding parameters
after calling SQLExecute for prepared statements.
WorkArounds=1073741824. Microsoft Access assumes that ORDER BY columns do not have to be in the SELECT list. This workaround addresses that mistaken assumption for data sources such as Informix and OpenIngres.
WorkArounds2=2. Some applications incorrectly specify the ColumnSize/DecimalDigits when binding timestamp parameters. This workaround causes the driver to ignore the ColumnSize/DecimalDigits specified by the application and use the database defaults instead.
WorkArounds2=4. Microsoft Access uses the most recent native type mapping, as returned by SQLGetTypeInfo, for a given SQL type. This workaround reverses the order in which types are returned, so that Access will use the most appropriate native type.
WorkArounds2=8. This workaround causes base to add the bindoffset in the ARD to the pointers returned by SQLParamData. This is to work around a MSDASQL problem.
WorkArounds2=16. This workaround causes the drivers to ignore calls to SQLFreeStmt(RESET_PARAMS) and only return success without taking other action. It also causes parameter validation not to use the bind offset when validating the charoctetlength buffer. This is to work around a MSDASQL problem.
WorkArounds2=24. If you are using a Connect ODBC flat file driver, such as dBase, under MSDASQL, you must use this workaround for the driver to operate properly.
WorkArounds2=32. Microsoft Access requires "DSN" to be included in a connection string. This workaround appends "DSN=" to a connection string, if it is not already included.
WorkArounds2=128. Some applications will open extra connections if SQLGetInfo(SQL_ACTIVE_STATEMENTS) does not return 0. This workaround causes SQLGetInfo(SQL_ACTIVE_STATEMENTS) to return 0 to avoid the overhead of these extra connections.
Microsoft Access and Visual Basic Users
---------------------------------------
We recommend that users of Microsoft Access and Visual Basic add the value pair WorkArounds=25 (1+8+16) for each data source they use with Access and Visual Basic. For data sources that support a single connection, add the line WorkArounds=29 (1+4+8+16).
Notes and Known Problems
The following are notes, known problems, or restrictions with version 3.60 of DataDirect Connect ODBC for Windows NT and Windows 9x.
Network Installations of Connect ODBC
-------------------------------------
This information is applicable only if you are performing a network installation instead of a typical installation of Connect ODBC. If the system from which the installation is being performed is running Windows 98 or Windows NT, using the Microsoft network client, and you are installing to a Novell server, then certain files will not be installed correctly. This is due to limitations in the network software. You .must obtain the latest version of the Novell network client and install it on your Windows 98 or Windows NT system to resolve the problem.
ODBC Driver Manager
-------------------
Connect ODBC 3.6 drivers require the 3.51 version of the ODBC Driver Manager (ODBC32.DLL and ODBCCP32.DLL). Because the ODBC 3.51 Driver Manager is compatible with 2.x compliant drivers, all 2.x versions of the Driver Manager should be removed from your access path to ensure application stability. Failing to remove older versions of the Driver Manager may result in application errors and abnormal terminations.
Installations of Connect ODBC
-----------------------------
When installing Connect ODBC, you cannot specify a driver installation directory path that contains spaces. A driver installation directory path is specified in the Driver Installation Directory window of the Setup program.
SQLColAttribute(s)
------------------
The column attributes 1001 and 1002, which were assigned as MERANT specific attributes, were inadvertently used as system attributes by the Microsoft 3.0 ODBC implementation. Applications using those attributes should now use 1901 and 1902 respectively.
SQL_C_NUMERIC
-------------
Because of inconsistencies in the ODBC specification, users attempting to use SQL_C_NUMERIC parameters should set the precision and scale values of the corresponding structure and the descriptor fields in the APD.
For Microsoft Access Users
--------------------------
Some SQL implementations, such as PROGRESS, do not allow queries to contain the COUNT function without the DISTINCT set quantifier. For example, "select COUNT(empid) from employees" is not a valid PROGRESS query. This type of query can be generated using Microsoft Access and will result in an error.
For MTS-DTC Users
-----------------
Distributed transaction support (MTS-DTC) is available only under
Windows NT 4.0.
The Microsoft Transaction Server must be installed on the NT 4.0 client on which you install the DTC-enabled ODBC drivers. Please install the Microsoft Transaction Server as follows:
1. Install NT Service Pack 3. (Service Pack 3 is specifically required by
the NT Options Pack 4.0)
2. Install NT Options Pack 4.0
3. You may now install NT Service Pack 4 or greater.
Because MTS-DTC runs as an NT service, the DTC-enabled ODBC drivers and the database clients that they require must be installed on a local hard drive.If you install the DTC-enabled ODBC drivers into a directory other than the default WinNT\system32 directory, then that directory must be on the System PATH.
For Btrieve Users
-----------------
The Btrieve driver may experience problems if the Btrieve Microkernel Engine's communication buffer size is smaller than the Btrieve driver's Array Size attribute. You can increase the communication buffer size with the BTI Database Setup Utility. You can decrease the array size option when you configure a data source using the ODBC Btrieve Setup dialog, or when passing a connection string.
For DB2 UDB Users
------------------
The DB2 UDB driver is described in the CONNECT ODBC REFERENCE SUPPLEMENT. Do NOT refer to the DB2 chapter in the CONNECT ODBC REFERENCE. The driver described in that chapter is not currently shipping.
For Flat File Users
------------------
If you are using a MERANT flat file driver, such as dBase, under
MSDASQL, youshould use WorkArounds2=24 as described in the previous section
"Driver Options."
For Informix Users
------------------
Restriction: Some Informix error messages may contain more than one error. It is unclear whether all errors displayed will be valid.
Attempting to use Microsoft Query '95 with the Informix driver will result in a protection fault from Query. This is because Query does not recognize the INTERVAL data types supplied by the driver. Users will need to obtain Microsoft Query '97 to obtain the fix.
For OpenIngres Users
--------------------
The OpenSQL option, which is available on t.he Advanced window, is not supported with MVS/DB2.
To execute properly, the ODBC API SQLProcedureColumns relies on the presence of the system view iiproc_params. If this view does not exist, your DBA should follow the instructions below to create the view.
1) Create a file iiproc.sql using the text between the lines below.
--------------------------------------------------------------------------------
drop view iiproc_params
\p\g
create view iiproc_params as
select procedure_name = p1.dbp_name,
procedure_owner = p1.dbp_owner,
param_name = p2.pp_name,
param_sequence = p2.pp_number,
param_datatype =
uppercase(iitypename(ii_ext_type(p2.pp_datatype,p2.pp_length))),
param_datatype_code = p2.pp_datatype,
param_length =
iiuserlen(ii_ext_type(p2.pp_datatype,p2.pp_length),(ii_ext_length(p2.pp_
datatype, p2.pp_length)*65536) +p2.pp_precision),
param_scale =int4(mod( p2.pp_precision, (256))),
param_nulls=charextract('YN', (mod(p2.pp_flags,2))+1),
param_defaults=charextract('YN',
(mod((p2.pp_flags/2),(2)))+1),
param_default_val=squeeze(d.defvalue)
from iiprocedure p1 , iiprocedure_parameter p2, iidefault d where
(p2.pp_procid1 = p1.dbp_id and p2.pp_procid2 = p1.dbp_idx)
and (p2.pp_defid1 = d.defid1 and p2.pp_defid2 = d.defid2)
\p\g
--------------------------------------------------------------------------------
2) Type: sql -U -u"$ingres" <vnode>::<database>
3) Once connected, type: \i iiproc.sql
Executing OpenIngres stored procedures with literals instead of parameters results in a syntax error:
SQLExecDirect:
In:hstmt = 0x00301250,
szSqlStr = "{call testproc (12345, 5,5, 'Ed')}", cbSqlStr = -3
Return: SQL_ERROR = -1
stmt: szSqlState = "37000", *pfNativeError = 0, *pcbErrorMst = 64
szErrorMst = "(MERANT)(ODBC INGRES driver) Syntax error or access
violation."
OpenIngres 2.0 client components are not available for Windows 9x yet; therefore, the OpenIngres 2.0 driver (IVOI215.DLL) can only be used on Windows NT.
For Oracle8 users
------------------
There is a known problem with Oracle8 servers earlier than version 8.04 that
causes both SQLDescribeParam and result set processing to fail when using stored
procedures in other userlists.
In addition, you must have NT Service Pack 4 installed on client and server machines. There are new MTS interfaces installed with this service pack that
are necessary for the Oracle8 driver. If you do not have this service pack
installed, enlistment in a DTC transaction will fail.
The MERANT Oracle8 ODBC driver uses the XA protocol support in Oracle8 to accomplish distributed transaction support. In order for recovery to work
properly, you must grant appropriate privileges on any server that will participate in a DTC transaction. You must grant the SELECT privilege on
SYS.DBA_PENDING_TRANSACTIONS to all users that will use MTS. See the Oracle8 documentation on using Oracle XA for details.
8.0.3 servers are not supported for distributed transactions, due to problems
with XA protocol support. You must use at least 8.0.4 servers.
For PROGRESS 7.3 and 8.0 Users
------------------
1) SQLRowCount will always return a value of either 0 or 1.
If multiple rows are affected by an UPDATE statement, SQLRowCount will return 1.
2) The length, precision, and scale attributes returned for derived columns are undefined.
3) Microsoft Access and Visual Basic users should set WorkArounds=1 as defined above in the Driver Options section. Furthermore, to avoid a Function Sequence error, do not attempt to update data until all rows have been read by Access.
4) When using scrollable multi-row cursors without the 7.3 or 8.1 server, deleted rows will not return the SQL_ROW_DELETED status. Instead, the deleted row will duplicate the values of the row that follows the deleted row in the result set.
The driver supports static cursors, using base emulation, and reports this .
correctly through SQLGetInfo.
THE -RO OPTION: The purpose of Progress's -RO option is to indicate that the
Progress Database itself is read-only, that is, the database resides on read-
only media, such as a CD-ROM. It means that all users would be connecting for
read-only, not that a particular connection would be read-only. The PROGRESS
documentation states that PROGRESS does not support servers for read-only users.
If you use the -RO parameter when other users are updating the database, you might see invalid data, such as stale data or index entries pointing to records that have been deleted. Because results cannot be guaranteed when the -RO is used to access a database on read/write media, this configuration can not be supported with the Connect ODBC PROGRESS driver.
For Microsoft SQL Server Users
-------------------------------
SQL Server does not support multiple active statements on a single connection by
default. A Microsoft Knowledge base document explaining how to enable multiple
active statements on a single connection with SQL Server through the use of
server side cursors is available at the following URL:
http://support.microsoft.com/support/kb/articles/q140/8/96.asp.
The SQL Server driver returns stored procedure names with the version number
appended to it. For example, a procedure defined as "proc1" will be returned as
"proc1;1".
The WorkArounds listed in the Driver Options section of this readme file are not
available for use with the Microsoft SQL Server ODBC driver.
For Microsoft SQL Server 6.5 Users Only
---------------------------------------
Attempting to execute DDL statements that contain errors will cause an implicit rollback of the current transaction if executing in manual commit mode. There is no warning that this has happened. This is a Microsoft SQL Server limitation and there is no driver WorkAround.
NOTE: When executing multiple statements in a stored procedure, the function SQLMoreResults will ignore all statements other than Select statements. Because the SQL Server and Sybase drivers do not have a way to prepare statements, the driver will not send those statements to the server until SQLExecute is called. Prepare will not return any of the normal errors that most of the drivers will return. If, however, the user requests information about result columns, the driver will execute a Select statement and return warnings or errors at SQLNumResultCols, SQLDescribeCol, or SQLColAttributes time.
The SQL Server 6 driver returns stored procedure names without the version
number appended to it. For example, a procedure defined as "proc1" is returned
as "proc1". If there is a group of procedures, a version number, such as ";2",
is appended.
If you have problems with the catalog functions returning incorrect data, you may need to upgrade your catalog stored procedures. Make sure that you have installed the latest version of the stored procedures, which are available from your database vendor. Refer to your SQL Server documentation for more information.
For Sybase Users
----------------
Sybase 4.9 server is supported only with Sybase Open Client 10.03 or greater in the 10.x series or 11.1.1 or greater in the 11.x series.
When using the Sybase driver to access a Sybase SQL Server version 4.9.2, you must install the Catalog Stored Procedures (CSPs) on the server to insure correct operation of the driver. To install the CSPs on your server, run the script file ivcsp492.sql included with the installation of the driver through the Sybase ISQL utility. The following is an example of the command line to run the script file:
isql -S<servername> -U<userid> -P<password> -iivcsp492.sql
where: <servername> is the name of your SQL Server, <userid> is a valid userid with write permission to the master database, and <pas.sword> is a valid password for <userid>.
If you encounter any problems running the script file, contact Sybase technical support at 1-800-8SYBASE.
You may experience a problem using catalog stored procedures when running the
driver with Sybase Adaptive Server 11.5 or 11.9.2. Contact Sybase for information about fixes.
The Sybase driver supports statements containing COMPUTE BY clauses. The results of the COMPUTE BY clause are handled as a separate result set. Use SQLMoreResults to process the additional result set.
For Text Users
--------------
Restriction: When encountering an invalid file, you may receive duplicate or
too many errors from SQLError.
For XML Users
--------------
The Table Hint and Row Hint fields on the Advanced tab of the setup dialog are
disabled for this release.
If you are connected via an HTTP URL, SQLTables and SQLColumns will return an
empty Rowset due to security restrictions imposed by HTTP.
Installing and Using the Online Documents
You can view the Online Documents with the Adobe Acrobat Reader version 3.0. Copies of this reader are provided on the CD for all product platforms. These versions are stored under the \READERS directory on the CD. You can also download the Acrobat Reader software from the Adobe Web site at no charge. The Adobe URL address is:
http://www.adobe.com/prodindex/acrobat/readstep.html
The Online Documents for DataDirect Connect ODBC are located under \BOOKS\ODBC\ on the CD. They are also available on the MERANT Web site. Opening the BOOKS.PDF file with the Acrobat Reader will allow you to select the CONNECT ODBC REFERENCE, the CONNECT ODBC REFERENCE SUPPLEMENT, or the CONNECT ODBC INSTALLATION GUIDE.
The DATADIRECT CONNECT ODBC REFERENCE is also available in bound hardcopy; contact MERANT for details on ordering.
For instructions about how to install and use the Online Documents and Acrobat Reader, refer to the booklet in the CD-ROM case or the MERANT Web site.
Installed Files
Setup copies the following files to the product installation directory, by default, \IVODBC:
IVSETUP.INF Uninstall directive file
PRODLIST.INI Installer file
QPROFILE.DLL Uninstall utility file
READ.ME This file
UNINST.ISU Uninstall initialization file
FIXES.TXT List of issues fixed in this release.
Setup copies the following files to the \IVODBC\TRANSLAT directory:
LIBMAIN.C
README.TRN Translation Library information file
TRANSLAT.C Sample Translation Library source file
WINNT.MAK Makefile for the Sample Translation Library
Setup copies the following files to your system directory (by default, the Windows \SYSTEM32 directory for Windows NT or \SYSTEM for Windows 9x):
MSVCRT.DLL Visual C 6.x Runtime Library
MSVCRT40.DLL Visual C 4.x Runtime Library
Setup copies the following files to the driver directory you have selected (by default, the Windows\SYSTEM32 directory for Windows NT or Windows\SYSTEM for Windows 9x). Help files have the extension .HLP; Table of Contents files have the extension .CNT. Resource files for each driver end in R.DLL; setup files for each driver end in S.DLL.
DBMSSOCN.DLL Microsoft network DLL for SQL Server
INIADX07.DLL Support DLL for XML driver
INIADX07R.DLL
INXMLX07.DLL Support DLL for XML driver
INXMLX07R.DLL
IVASE15.CNT
IVASE15.DLL Sybase ASE 12.0 driver
IVASE15R.DLL
IVASE15S.DLL
IVASE15.HLP
IVBAS15.DLL MERANT ODBC common library
IVBAS15R.DLL
IVBTR15.CNT
IVBTR15.DLL Btrieve (Pervasive.SQL) driver
IVBTR15R.DLL
IVBTR15S.DLL
IVBTR15.HLP
IVCSP492.SQL Sybase script that installs the Catalog Stored
Procedures (CSPs)
IVDBF15.CNT
IVDBF15.DLL dBASE driver
IVDBF15R.DLL
IVDBF15.HLP
IVDRV15.CNT Driver Reference Help Contents file
IVDRV15.HLP Driver Reference Help file
IVFLT15.DLL MERANT flat-file ODBC driv.er shared library
IVFLT15R.DLL
IVGUP15.CNT
IVGUP15.DLL SQLBase driver
IVGUP15R.DLL
IVGUP15S.DLL
IVGUP15.HLP
IVIDP15.CNT
IVIDP15.DLL Paradox driver
IVIDP15R.DLL
IVIDP15S.DLL
IVIDP15.HLP
IVINF15.CNT
IVINF15.DLL Informix driver
IVINF15R.DLL
IVINF15S.DLL
IVINF15.HLP
IVINFDTC15.DLL
IVINFO.EXE Returns licensing and product information
IVMSNMP.DLL Microsoft Named Pipes DLL for Sybase ASE
IVMSSS15.DLL SQL Server driver for Microsoft SQL Server
IVMSSS15D.DLL
IVMSSS15R.DLL
IVMSSS15S.DLL
IVODBC.LIC MERANT ODBC driver license file
IVOI215.CNT
IVOI215.DLL OpenIngres 2.0 driver
IVOI215R.DLL
IVOI215S.DLL
IVOI215.HLP
IVOING15.CNT
IVOING15.DLL OpenIngres driver
IVOING15R.DLL
IVOING15S.DLL
IVOING15.HLP
IVOR715.CNT
IVOR715.DLL Oracle driver
IVOR715R.DLL
IVOR715S.DLL
IVOR715.HLP
IVOR815.CNT
IVOR815.DLL Oracle8 driver
IVOR815R.DLL
IVOR815S.DLL
IVOR815.HLP
IVOR8DTC15.DLL
IVPRO15.CNT
IVPRO15.DLL PROGRESS driver
IVPRO15R.DLL
IVPRO15S.DLL
IVPRO15.HLP
IVSS615.CNT
IVSS615.DLL SQL Server 6 driver for Microsoft SQL Server
IVSS615R.DLL
IVSS615S.DLL
IVSS615.HLP
IVSYB15.CNT
IVSYB15.DLL Sybase driver
IVSYB15R.DLL
IVSYB15S.DLL
IVSYB15.HLP
IVSYBDTC15.DLL
IVTRN15.DLL MERANT sample translation DLL
IVTXT15.CNT
IVTXT15.DLL Text driver
IVTXT15R.DLL
IVTXT15.HLP
IVUDB15.CNT
IVUDB15.DLL DB2 UDB driver
IVUDB15R.DLL
IVUDB15S.DLL
IVUDB15.HLP
IVUTL15.DLL MERANT ODBC utility DLL
IVUTL15R.DLL
IVWNSCK.DLL Winsock DLL for Sybase ASE
IVXLWB15.CNT
IVXLWB15.DLL Excel Workbook driver
IVXLWB15R.DLL
IVXLWB15.HLP
IVXML15.CNT
IVXML15.HLP XML driver
IVXML15.DLL
IVXML15R.DLL
IVXML15S.DLL
INXMLX07.CNT
INXMLX07.DLL
MSXMLR.DLL Microsoft XML parser
PROSQL32.DLL PROGRESS Client Library
QECSV1.BND Bind files for the DB2 UDB driver
QECSWHV1.BND
QERRV1.BND
QERRWHV1.BND
QEURV1.BND
QEURWHV1.BND
SQLSODBC.HLP SQL Server driver help
For information on the files that are installed when you install the MDAC 2.1 runtime components, please see the following Microsoft web site:
http://www.microsoft.com/data/MDAC21info/manifest_intro.htm
End of READ.ME.