	QDREAD.ME
	INTERSOLV DataDirect ODBC Drivers for Explorer 1.0
	Driver Version 2.10
	September 1995

This README file contains database driver information not included 
in the INTERSOLV DataDirect ODBC Drivers Reference or the online help 
for this release.  This file contains information about the following 
topics:

What's New in Version 2.10
Available DataDirect ODBC Drivers
Files Installed
Solving Connection Problems with DLL Manager
Notes and Known Problems


	What's New in Version 2.10

The following list summarizes the new drivers and features in version 2.10. 

New Drivers
- New DB2/2 driver (QEDB207.DLL) for Windows 3.1 

All Drivers
- Now fully compliant with version 2.10 of the ODBC specification
- Now support translation DLLs

Flat-File Drivers (Btrieve, dBASE, Excel, Paradox, and Text)
- Now support the SQLSetPos function
- Now support subqueries in INSERT statements 
- Many queries are optimized so that they execute faster. 
  For example, OR'ed predicates may now use indexes.

Btrieve Driver
- Incorporates enhanced performance for many user applications

INFORMIX 5 Driver
- Now support databases that do not have transaction logging enabled
- Offer an option to support scrollable cursors
- Uses tables from different databases via database qualifiers

INGRES 6.4/04 Driver
- Includes many performance tuning options
- No longer requires that you set the II_DATE_FORMAT environment 
  variable to US

Paradox Drivers
- Now support the SQLPrimaryKeys function

Scalable SQL Driver (formerly Netware SQL driver)
- Now supports multiple connections when connecting to a 3.1 server 

SQLBase Driver
- Now supports SQLBase 6.x and includes support for SQLBase stored 
  procedures

System 10 Driver
- Offers many new performance tuning options 


	Available DataDirect ODBC Drivers

The following drivers are available:

Driver			Supports
------			--------
ALLBASE			ALLBASE/SQL, IMAGE/SQL

Btrieve			Btrieve versions 5 and 6.x

DB2/2			DB2/MVS, SQL/400, and SQL/DS (through the DDCS/2 
			or DDCS/6000 gateway), DB2/2, DB2/6000--supporting 
			the use of the Client APplication Enabler (CAE) 1.2 
			interfaces

Previous DB2/2		Same database systems as above supporting the use
(This driver will not	CAE 1.0 interfaces
be supported in 
future releases.)			

dBASE		 	dBASE II, III, IV, and V files, Clipper 
			files, FoxBASE files, FoxPro files 
			versions 1, 2.5

Excel 4			Excel 2, 3, and 4 .XLS files

Excel 5			Excel 5 .XLS Workbook files

INFORMIX 4		INFORMIX via INFORMIX-Net 4.x

INFORMIX 5 		INFORMIX via INFORMIX-Net 5.x

INGRES (This driver 	INGRES 6.4/03
will not be supported
in future releases.)

INGRES 6.4/04 		INGRES 6.4/04 or 6.4/05

InterBase		InterBase

MicroDecisionware	DB2 and Teradata (MDI gateway)

Oracle 6 		Oracle 6

Oracle 7 		Oracle 7

Paradox 4		Paradox versions 3-4.5

Paradox 5		Paradox versions 3-5

PROGRESS 		PROGRESS 6

Scalable SQL 		Scalable SQL versions 3.x

SQL Server 		SQL Server 4.2 from Microsoft and Sybase

SQLBase 		Gupta SQLBase 5.2 and 6.0

Sybase System 10 	Sybase System 10

Text 			ASCII Text files

XDB 			XDB versions  3, 4


	Driver Files Installed

The following database drivers and supporting files are copied to the 
Driver Install Directory (by default, C:\WINDOWS\SYSTEM) specified 
during Explorer Setup:

CORE3WIN.DLL	Oracle support DLL
COREWIN.DLL	Oracle support DLL
CTL3D.DLL
CTL3DV2.DLL	Microsoft 3D controls, version 2
LDLLSQLW.DLL	INFORMIX client-side API
NLS23WIN.DLL
ODBC.DLL	Microsoft ODBC Driver Manager
ODBCCURS.DLL	Microsoft ODBC Cursor Library DLL
ODBCINST.DLL	Microsoft ODBC Driver installation DLL
ODBCINST.HLP
ORA6WIN.DLL	Oracle version 6.x client-side API
ORA71WIN.DLL	Oracle version 7.1 client-side API
ORA7WIN.DLL	Oracle version 7.0 client-side API
QEBAS07.DLL	INTERSOLV ODBC driver shared library
QEBTR07.DLL	Btrieve driver
QEBTR07.HLP
QECSV1.BND	DB2/2 SQL bind file
QECSWHV1.BND	DB2/2 SQL bind file
QEDB207.DLL	DB2/2 driver
QEDB207.HLP
QEDBF07.DLL	dBASE driver
QEDBF07.HLP
QEDBM07.DLL	DB2/2 driver
QEDBM07.HLP
QEFLT07.DLL	INTERSOLV flat-file ODBC driver shared library
QEGUP07.DLL	SQLBase driver
QEGUP07.HLP
QEHP07.DLL	ALLBASE driver
QEHP07.HLP
QEIDP07.DLL	Paradox 5 driver
QEIDP07.HLP
QEINF07.DLL	INFORMIX 4 driver
QEINF07.HLP
QEINF507.DLL	INFORMIX 5 driver
QEINF507.HLP
QEINFO.EXE
QEING07.DLL	INGRES 6.4/03 driver
QEING07.HLP
QEING407.DLL	INGRES 6.4/04 driver
QEING407.HLP
QEINT07.DLL	InterBase driver
QEINT07.HLP
QEMDI07.DLL	MicroDecisionware driver
QEMDI07.HLP
QEODBC.LIC	INTERSOLV ODBC driver license file
QEOR707.DLL	Oracle 7 driver
QEOR707.HLP
QEORA07.DLL	Oracle 6 driver
QEORA07.HLP
QEPDX07.DLL	Paradox 4 driver
QEPDX07.HLP
QEPRO07.DLL	PROGRESS driver
QEPRO07.HLP
QERRV1.BND	DB2/2 SQL bind file
QERRWHV1.BND	DB2/2 SQL bind file
QESS07.DLL	SQL Server driver
QESS07.HLP
QESYB07.DLL	Sybase System 10 driver
QESYB07.HLP
QETRN07.DLL	INTERSOLV translation DLL
QETXT07.DLL	Text driver
QETXT07.HLP
QEURV1.BND	DB2/2 SQL bind file
QEURWHV1.BND	DB2/2 SQL bind file
QEUTL07.DLL	INTERSOLV ODBC driver utility DLL
QEXDB07.DLL	XDB driver
QEXDB07.HLP
QEXLS07.DLL	Excel 4 driver
QEXLS07.HLP
QEXLS507.DLL	Excel 5 driver
QEXLS507.HLP
QEXQL07.DLL	Scalable SQL driver
QEXQL07.HLP
RDS.IEM		INFORMIX error message file
SPYREAD.ME	Dr. DeeBee Spy text READ.ME file
SQL.IEM		INFORMIX error message file
USDMEM.DLL
WBTRCALL.DLL	Btrieve engine (local version)
WDDLSVCS.DLL	Btrieve utility DLL
WXQLCALL.DLL	Novell Scalable SQL client-side API


	Solving Connection Problems with DLL Manager

INTERSOLV supplies a tool called DLLMGR, which is primarily for 
INTERSOLV Technical Support use.  DLLMGR is not a supported product 
and is provided on an as-is, use-at-your-own-risk basis.  This tool lists 
the DLLs that are loaded in memory.

DLLs (dynamic link libraries) are the software components used by the 
ODBC Driver Manager to connect to your DBMS server from your client 
workstation.  The ODBC drivers are implemented as DLLs, and they call 
other DLLs provided by your DBMS vendor for network access.  

Unfortunately, if the Microsoft ODBC Driver Manager cannot locate the 
required DLLs on your system, the error messages generated do not 
identify which DLLs are missing.

Since the ODBC Driver Manager provides no indication of the problem 
when it cannot load a DLL, simple problems such as an inadequate DOS 
PATH specification can be hard to solve.  DLLMGR is useful for 
determining which required DLLs are missing when your application cannot 
connect to the specified data source.  When DLLMGR cannot load a DLL, it 
reports which files it cannot find.

If your ODBC application cannot load a driver DLL:

1  Double-click the DLLMGR icon.  

2  Choose the Load... command from the File menu. 

3  Type or select the name of the DLL you want to load.

4  Click OK.

DLLMGR then displays a message for each DLL that it cannot find.  

Consult your DBMS vendor's documentation, your network administrator, or 
your database administrator to locate the missing DLLs.

If DLLMGR identifies the driver (QExxxnn.DLL, where xxx is identifies the 
DBMS the driver connects to, as in INF for Informix, and nn is the 2-digit 
revision number of the driver) as the missing component, perform the 
following:

1  Check that you spelled the driver file name and path correctly 

2  Our drivers are installed in your Windows \SYSTEM directory unless 
   you relocated them after installation.  If you did relocate them, be sure 
   that the directory you installed them in is on your DOS $PATH.

3  If you cannot locate the correct driver on your system, reinstall the 
   ODBC Pack from the original source disks.


	Notes and Known Problems


For Btrieve Users
----------------------
Note:  INTERSOLV ships the 5.x local version of WBTRCALL.DLL.  For 
information on the latest 6.x Btrieve release, contact Btrieve Technologies.
There are two versions of 5.x WBTRCALL.DLL:  networked and not 
networked.  INTERSOLV supplies the not networked version when you 
install the Btrieve driver.  If you want network access, you must get the 
networked version from Btrieve Technologies.

If you are already using networked Btrieve, do not install the  
INTERSOLV version of WBTRCALL.DLL, because it does not support 
network access. When the Setup program asks whether you wish to overwrite 
WBTRCALL.DLL, answer No.

Note:  The Btrieve driver supports transactions.  However, to use its 
transaction processing capabilites, you must change certain settings in the 
WIN.INI or BTI.INI file.  For more information, double-click the ODBC 
Driver Help icon, click the Btrieve driver, and then click the topic 
"Installing Btrieve to Process Transactions."


For Teradata Users
----------------------
Restriction:  ODBC Developers can code against Teradata as long as they do 
not request any table or column information.  This is because ODBC catalog 
functions (such as SQLTables) do not work with Teradata.

Restriction:  Users of ODBC-compliant applications such as Access or Excel, 
which automatically make ODBC catalog function calls, cannot use the 
MicroDecisionware driver for Teradata access.  They receive syntax errors 
when the application makes catalog function calls.  


For Paradox Users
----------------------
Problem:  Paradox users should avoid updating values in primary key fields 
when running transactions with ReadConsistency=1.  Primary key violations 
will not be detected until the changes are committed.  For example, if you 
insert the same row twice in your transaction, and then try to commit your 
transaction, you receive a primary key violation error.  

Workaround:  To update values in primary key fields, do not have 
ReadConsistency=1 during a transaction.  Instead, use the autocommit mode.


For SQL Server and System 10 Users
----------------------
The following topics apply to users of Microsoft SQL Server, Sybase 
SQL Server, and Sybase System 10.

Note:  If you have problems with the catalog functions returning incorrect 
data, you may need to upgrade your catalog stored procedures.  In particular, 
the SQL Server version 4.2 procedures do not provide enough information for 
many of our catalog functions to work properly.  Make sure 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.

Note:  When executing multiple statements in a stored procedure, the 
function SQLMoreResults will ignore all statements other than Select 
statements. Since the SQL Server and Sybase drivers do not have a way to 
prepare statements, the driver will not send that statement to the server 
until SQLExecute is called.  Prepare will not return any of the normal 
errors that most of the drivers will return.  However, if 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.

Restriction:  When setting up data sources for System 10 using the ODBC
Setup dialog, the database name can be no longer than 10 characters.


End of QDREAD.ME
