ODBC Drivers Frequently Asked Questions

Couldn't find the answer to your question? Take a look at our support forum.

Licensing and Subscriptions

Am I entitled to distribute applications written with Devart's ODBC drivers?

If you have purchased a full version of a driver, you are entitled to distribute the driver with pre-compiled programs created with its use. You are not entitled to sell any components or libraries inherited from the driver or using its source code. For more information see the License.rtf file in the installation directory of the driver.

I have a registered version of a driver. Will I need to pay to upgrade to future versions?

After ODBC Driver for Oracle 4.00, ODBC Driver for SQL Server 4.00, ODBC Driver for MySQL 4.00, ODBC Driver for InterBase and Firebird 2.00, and for ODBC Driver for PostgreSQL all upgrades to future versions are free to users with an active Subscription.

Users that have a registration for previous versions of a driver will have to first upgrade to jump in on the Subscription program.

What are the benefits of the Subscription Program?

The Subscription Program is an annual maintenance and support service for users of Devart ODBC drivers.

Users with a valid Subscription get the following benefits:

Priority Support is an advanced product support program which offers you expedited individual assistance with product-related questions from the developers themselves. Priority Support is carried out over email and has a two business day response policy.

The Subscription Program is available for registered users of ODBC Driver for Oracle 4.00, ODBC Driver for SQL Server 4.00, ODBC Driver for MySQL 4.00, ODBC Driver for InterBase and Firebird 2.00, and for ODBC Driver for PostgreSQL 1.00 and higher.

Can I use my version of the driver after my Subscription expires?

Yes, you can. Driver version licenses are perpetual.

I want a driver Subscription! How can I get one?

An annual driver Subscription is included when ordering or upgrading to any registered (non-Trial) edition of ODBC Driver for Oracle 4.00, ODBC Driver for SQL Server 4.00, ODBC Driver for MySQL 4.00, ODBC Driver for InterBase and Firebird 2.00, and for ODBC Driver for PostgreSQL 1.00 and higher.

You can renew your driver Subscription. For more information, please contact sales@devart.com.

Does this mean that if I upgrade to ODBC Driver for Oracle 4 from ODBC Driver for Oracle 3, I'll get an annual ODBC Driver for Oracle Subscription for free?

Yes. You will also get an annual Subscription for free when you upgrade to ODBC Driver for SQL Server 4, ODBC Driver for MySQL 4, or ODBC Driver for InterBase and Firebird 2.

How do I upgrade to the new version of the driver?

To upgrade to ODBC Driver for Oracle 4.00, ODBC Driver for SQL Server 4.00, ODBC Driver for MySQL 4.00, ODBC Driver for InterBase and Firebird 2.00, you can get a Version Update from an Ordering Page of a particular product. For more information, please contact sales@devart.com.

General Questions

What software should be installed on a client computer so that my applications that use Devart's dbExpress drivers can run?

Firstly you should take care of the driver itself to be presented on the client computer. Other items depend on the driver you are using: ODBC Driver for Oracle: You do not need any additional files if the driver works in Direct mode. Otherwise, you should install the Oracle client.

ODBC Driver for SQL Server: You should have OLE DB provider installed on the client. In current versions of Microsoft Windows, as Windows 2000, OLE DB is already included. But it is highly recommended to download latest version of Microsoft Data Access Components (MDAC).
If you work with SQL Server Compact Edition, the server itself should be installed on the client computer.

ODBC Driver for MySQL: Generally you do not need any additional files to be installed. Below you can see the only exceptions:

ODBC Driver for InterBase and Firebird: You should install the InterBase or Firebird client.

ODBC Driver PostgreSQL: You do not need any additional files.

I would like to develop an application that works with database. Should I use VCL Data Access Components, or dbExpress drivers?

dbExpress technology serves for providing a more or less uniform way to access different servers (Oracle, SQL Server, MySQL, and so on). It is based on drivers that include server-specific features. Like any universal tool, in many specialized cases dbExpress providers lose some functionality. For example, the dbExpress design-time is quite poor and cannot be expanded.

Our Data Access Components (DACs) are specialized sets of components for specific servers, which have advanced server-specific design-time editors, and a component interface similar to that of BDE.

We tried to include maximal support of server-specific features in both dbExpress drivers and DACs. However, the nature of dbExpress technology has some restrictions that cannot be overcome.

DACs and dbExpress drivers use the same kernel and thus have similar performance. In some cases dbExpress is slower because data undergoes additional conversion to correspond to dbExpress standards.

To summarise, if it is important for you to be able to quickly adapt your application to different database servers, it is probably better to use dbExpress drivers. In other cases, especially when migrating from BDE or ADO, you should use DACs.

There are several dll files in the installation directory of the driver. Which one should I use in my application?

It depends on the version of your IDE:

The X letter in the file name depends on your driver.

How can I set the port number to be used by connecting to the server?

ODBC Driver for MySQL, ODBC Driver PostgreSQL: You can set the port number in two ways:

ODBC Driver for InterBase and Firebird: You can set the port number in the Database parameter using the following format: HostName/Port:DBPath

When I try to run my application that uses Devart dbExpress driver, I see the "Unable to load dbexp*.dll" message.

The dbexp*.dll file is the driver itself. This file should be located in any folder accessible for your application written with its use. When you deploy your application, copy dexp*.dll to a directory included into the PATH system variable, or to the directory with your application.
The full name of the dexp*.dll file depends on your driver, and your IDE.