	READ.ME
	INTERSOLV DataDirect ODBC Oracle 7 Driver for Windows 3.1
	Version 2.10
	August 1, 1995

NOTE: The Oracle 7 driver you have received is a 90-day evaluation
copy. The driver is fully functional. To order the Oracle 7 or
other INTERSOLV DataDirect ODBC drivers, call INTERSOLV:

USA and Canada    800-547-4000
Asia and Pacific  301-838-5241
United Kingdom    +44 1727 812812
Australia         +61 (3) 9816 9977
France            +33 (1) 49.03.09.99
Germany           +49 (89) 962 71-152
Other countries   +44 1727 812812
 
For complete information about the functionality
of this driver, see the Oracle 7 help file (OROR707.HLP). 

This READ.ME file contains information about the following topics:

What's New in Version 2.10
Available DataDirect ODBC Drivers
Driver Options
	Microsoft Access and Visual Basic Users
Solving Connection Problems with DLL Manager


	What's New in Version 2.10

The following list summarizes the new features in version 2.10. 

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


	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 Options

INTERSOLV has included nonstandard options to the drivers that enable 
you to take full advantage of them.

To use these options, we recommend that you create a separate data 
source for each application.  Open the ODBC.INI file, and, under the 
section for the data source you created, add the line WorkArounds=n.  Add 
the values together to obtain more than one option.

WorkArounds=1.  If an ODBC driver reports to Access 1.1 that its 
SQL_CURSOR_COMMIT_BEHAVIOR or SQL_CURSOR_ROLLBACK_BEHAVIOR is 0, then 
Access opens tables read-only.  If this option is on, our ODBC drivers 
return 1, allowing Access to open tables read-write.

WorkArounds=2.  Some applications cannot handle database qualifiers.  If 
this option is on, the driver reports that qualifiers are not supported.  

WorkArounds=4.  Visual Basic 3.0 sometimes requires two connections to 
a database system.  Since some database systems support only one 
connection, the second 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.  If an ODBC driver in SQLStatistics reports to Access 
1.1 an INDEX_QUALIFIER that contains a period, Access raises a 
"tablename is not a valid name" error.  Turning this option on causes the 
driver to return no INDEX_QUALIFIER, allowing Access to open the table.

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=512.  To prevent ROWID results, this option forces the 
SQLSpecialColumns function to return a unique index as returned from 
SQLStatistics.

WorkArounds=65536.  This option strips trailing zeros from decimal results, 
which prevents MS Access from raising 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>.

Microsoft Access and Visual Basic Users
---------------------------------------
We recommend that users of Microsoft Access 1.1 and Visual Basic 3.0 
add the line 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).


	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.

End of READ.ME
