This file describes the areas of the Easysoft ODBC-ODBC Bridge on
Microsoft Windows which differ from other operating systems.

Windows NT
----------

For Windows NT the Easysoft ODBC-ODBC Bridge Server is an installed
service which may be started/stopped from Control Panel->Services.

Windows 95
----------

For Windows 95, you must start the Easysoft ODBC-ODBC Bridge Server
manually by selecting esoobserver from Start Menu->Easysoft->ODBC-ODBC
Bridge.

You must be running Winsock 2 to use the Easysoft ODBC-ODBC Bridge.
If you are not running Winsock 2 it is available as a download from
Microsoft's web page at http://www.microsoft.com.

Services entry
==============

The OOB Server does not require an entry in the services file to
function corrrectly but if you want to see the service name displayed
by netstat instead of the port number you can edit the services file.
Adding this entry also reserves the port for the OOB Server.

The services file is usually located in the
"c:\<NT install directory>\system32\drivers\etc"
directory on Windows NT.

Edit the "services" file with any Windows text editor, such as
Notepad.  The OOB service should be defined as "8888/TCP" assuming
you accepted the default port of 8888 during installation. The entry
should look like:

esoobserver            8888/tcp

Accessing MS Windows ODBC datasources
-------------------------------------

When setting up a data source name (DSN) on MS Windows please
remember you can only access SYSTEM DSNs from other machines.

If you get an error on connection (e.g. IM002) check and double-check
the following:

[1] Make sure the DSN you are trying to access is a SYSTEM DSN.

[2] Make sure you are using the correct DSN name.

[3] Make sure you are using the correct username and password to log
    on to the Windows machine (e.g. a your NT domain username/password).
    These must be assigned to the odbc.ini attributes LogonUser and
    LogonAuth or specified in the SQLDriverConnect connection string.

[4] Make sure you are using the correct database username and
    password. These are specified in as the odbc.ini attributes TargetUser
    and TargetAuth or as UID and PWD in the SQLDriverConnect connection
    string.

[5] Make sure the database exists and the database engine is running.

If you get a message such as:

28000:1:1326:[Easysoft ODBC (Client)]Invalid authorization specification

the third number is the ODBC driver native error code. You can look
this up in the OOB FAQ to determine the problem e.g. account expired
or locked out.

Once you have checked the above test the DSN from the Windows machine
using any ODBC application you have available (e.g. MS Access, Excel
etc).
