Using EASYLABEL and a PARADOX 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 trying to connect to a Paradox database file using an ODBC driver, a “File access denied” error occurs.

Cause:
The “File access denied” error occurs if the Paradox 3.5 file is password-protected.

Solution:
Microsoft has confirmed this to be a compatibility problem between the Paradox ODBC driver version 1.0 and Paradox version 3.5. Upgrade the ODBC driver to version 2.0 or higher.

Problem:
An ‘Invalid or Missing Password’ message appears when trying to connect to a Paradox database file. The message occurs under the field specification screen even though the Paradox data file is not password protected.

Cause:
The message occurs because the Paradox ODBC driver is incompatible with the Paradox database file. The Paradox ODBC version 1.0 driver that is from Microsoft only supports Paradox version 3.5.

Solution:
There are two workarounds:
1) Obtain a newer ODBC driver from a third-party vendor.
2) Save the Paradox database file as version 3.5.

Problem:
When attempting to print a format that uses a Paradox database, a ‘No primary index’ message appears.

Cause:
The index file for the Paradox database is corrupt or is not in the same sub-directory as the database file.

Solution:
Re-create the index file associated with the Paradox database.