Interoperability Issues

Interoperability issues can occur when you have a working ODBC application in place. In these cases, the issue occurs in one or more of the following components of ODBC-the ODBC application, ODBC driver, ODBC Driver Manager, and/or data source. Refer to "What Is ODBC?" in "Using The Product" of the DataDirect Connect for ODBC and Connect XE for ODBC User's Guide for an explanation of the components of ODBC.

Some common examples of what you might experience if you have an interoperability issue are:

SQL statements fail to execute.
Data is returned/updated/deleted/inserted incorrectly.
A hang or core dump.

Troubleshooting the Issue

When you experience an interoperability issue, you must isolate the component in which the issue is occurring. Is it an ODBC application, an ODBC driver, an ODBC Driver Manager, or a data source issue?

The first step

Test to see if your ODBC application is the source of the problem. To do this, replace your ODBC application with a simpler application. If you can reproduce the issue using a simpler ODBC application, then you know your ODBC application is not the cause of the issue.

On Windows, you can use ODBC Test, which is part of the Microsoft ODBC SDK, or the example application that is shipped with DataDirect Connect and Connect XE for ODBC drivers. See "ODBC Test" and "The example Application" for details.

On UNIX and Linux, you can use the example application that is shipped with DataDirect Connect and Connect XE for ODBC drivers. See "The example Application" for details.

The second step

Test to see if the data source is the source of the problem. To do this, use the native database tools that are provided by your database vendor.

The third step

If you find that neither the ODBC application nor the data source is the source of your problem, troubleshoot the ODBC driver and the ODBC Driver Manager.

In this case, we recommend that you create an ODBC trace log to can provide to DataDirect technical support. See "ODBC Trace" for details.