Using EASYLABEL and an ORACLE Open Database Connectivity (ODBC) Driver


The purpose of this document is to provide troubleshooting information when using an ODBC driver with EASYLABEL.

Section I. Identifies some common issues that pertain to the ODBC driver setup.
Section II.Identifies some common issues that pertain to EASYLABEL and connection to the data file specified in the ODBC driver setup.

I. Common issues pertaining to the ODBC driver setup.

Symptom:
Data Source Name is not listed in EASYLABEL’s “DATABASE SYSTEM” selection box.

Common Causes:
– the ODBC driver is not installed.
– the ODBC driver is installed; however the path for the data source is incorrect.

Symptom:
The data file name is not listed in EASYLABEL’s “TABLE NAME” selection box.

Common Causes:
– the ODBC driver version is incompatible with the application version
– the path in the ODBC driver setup is incorrect.
– the data file is already open and the ODBC driver cannot display an open file.

Symptom:
EASYLABEL cannot display the field names.

Common Causes:
– if there are any index files associated with the data file, the index files may be corrupt.
– the data file may be corrupt.

II. Issues regarding EASYLABEL and the data file.

Problem:
When attempting to create a field that uses an ORACLE database, the message ‘Driver specified by data source could not be loaded’ appears.

Cause:
The ODBC Driver Manager is attempting to load the ODBC ORACLE driver (SQORA.DLL). The ODBC ORACLE driver (SQORA.DLL) loads ORA6WIN.DLL to connect to the ORACLE server. The message appears if the ORACLE driver cannot find ORA6WIN.DLL or finds the wrong version of ORA6WIN.DLL.

Solution:
1. Search for and delete old versions of ORA6WIN.DLL. The correct version of the ORA6WIN.DLL was installed by the ODBC ORACLE driver and is located in the subdirectory \windows\system.
2. Make sure that ORA6WIN.DLL was installed when the ODBC ORACLE driver was installed.

Problem:
When attempting to create a field that uses and ORACLE database, the message ‘No interface driver connected — function not performed’ appears.

Cause:
The ODBC ORACLE driver cannot find ORA6WIN.DLL or one of the SQL*Net components.

Solution:
1. Without running the ODBC ORACLE driver, make sure the network connection is valid. For example, type “ping ” for a TCP/IP connection.
2. Search for and delete old versions of ORA6WIN.DLL. The correct version of the ORA6WIN.DLL was installed by the ODBC ORACLE driver and is located in the subdirectory \windows\system.
3. Check that the PATH variable contains the BIN subdirectory of the directory (usually C:\ORACLE6\BIN or C:\ORAWIN\BIN).
4. Check that the CONFIG_FILES variable is set in your AUTOEXEC.BAT file and that it points to your ORACLE configuration file (ORACLE.INI). If you are using MS-DOS 6.0, check that the CONFIG environment variable is either not set or is cleared in the last line of your AUTOEXEC.BAT file.
5. Check that SQLTCP.DLL (for TCP/IP), SQLSPX.DLL (for Novell NetWare IPX/SPX), or SQLNMP.DLL ( for Named Pipes) is in the ORACLE BIN directory specified in the PATH statment. (If not, SQL*Net was not installed correctly.)
6. Check that ORA7WIN.DLL and COREWIN.DLL are in the ORACLE BIN directory specified in the PATH statment. (If not, SQL*Net was not installed correctly.)

Problem:
When attempting to create a field that uses an ORACLE database, the message ‘Network driver not loaded’ appears.

Cause:
This error can occur when ORA6WIN.DLL is loaded but cannot find another SQL*Net component, such as SQLTCP.DLL.

Solution:
1. Check that the directories containing the SQL*Net components are in your PATH statement.
2. Check that the ORACLE_HOME variable is set correctly in your C:\WINDOWS\ORACLE.INI file.
If ORACLE Server version 6 was already installed on your system, ORACLE_HOME should be set twice. The first time, it should be set to your version 6 directory, usually C:\ORACLE6. The second time, in the [Oracle] section of the file, it should be set to C:\ORAWIN.
If ORACLE Server was not installed on your system, ORACLE_HOME should be set to C:\ORAWIN.
3. Search for and delete old versions of ORA6WIN.DLL. The correct version of the ORA6WIN.DLL was installed by the ODBC ORACLE driver and is located in the subdirectory \windows\system.
4. Check that you have followed all the instructions for the SQL*Net driver you are using. For example, for the SQL*Net for TCP/IP driver, make sure that all the TSRs, such as NMTSR and SOCKTSR, are loaded. (If not, SQL*Net was not installed correctly.)

Problem:
When attempting to print a format that uses an ORACLE database, the message ‘Message Not Found’ appears.

Cause:
The ODBC ORACLE driver searches for error messages in the subdirectory that normally contains all ORACLE version 6 error message files.

Solution:
The ODBC ORACLE driver cannot find the list of error messages to display. To fix this:
1. Check that the CONFIG_FILES variable is set in your AUTOEXEC.BAT file and that it points to your ORACLE configuration file (ORACLE.INI). If you are using MS-DOS 6.0, check that the CONFIG environment variable is either not set or is cleared in the last line of your AUTOEXEC.BAT file.
2. Check that the ORACLE_HOME variable is set correctly in your C:\WINDOWS\ORACLE.INI file.
If ORACLE Server version 6 was already installed on your system, ORACLE_HOME should be set twice. The first time, it should be set to your version 6 directory, usually C:\ORACLE6. The second time, in the [Oracle] section of the file, it should be set to C:\ORAWIN.
If ORACLE Server was not installed on your system, ORACLE_HOME should be set to C:\ORAWIN.
3. If you did not have any ORACLE software on your workstation, make sure that you copied all the .MSB files from C:\ORAWIN\RDBMS70 to C:\ORAWIN\DBS.
The ODBC ORACLE driver should now be able to print the ORACLE Server error message, enabling you to fix the problem that generated the error.