Version String Information

All drivers have a version string of the format:

X.YY.ZZZZ(BAAAA, UBBBB) 

or

XX.YY.ZZZZ(bAAAA, uBBBB)

The Driver Manager on UNIX and Linux has a version string of the format:

XX.YY.ZZZZ(UBBBB) 

The component for the Unicode conversion tables (ICU) has a version string of the format:

XX.YY.ZZZZ

where:

XX is the major version of the product.

YY is the minor version of the product.

ZZZZ is the build number of the driver or ICU component.

AAAA is the build number of the driver's bas component.

BBBB is the build number of the driver's utl component.

For example:

5.3.0001 (B0001, U0002) 
    |__|  |___|  |___| 
   Driver  Bas    Utl 

On Windows, you can check the version string through the properties of the driver DLL. Right-click the driver DLL and select Properties. The Properties dialog box appears. On the Version tab, click File Version in the "Other version information" list box.

You can always check the version string of a driver by looking at the About tab of the driver's Setup dialog.

On UNIX, you can check the version string by using the ddtestlib tool shipped with the product. This tool is located in install_directory/bin.

Use the following command line:

ddtestlib shared_object 

For example, for the Oracle Wire Protocol driver:

ddtestlib ddora23.so 
5.3.0001 (B0001, U0002) 

For example, for the Driver Manager:

ddtestlib libodbc.so 
5.3.0001 (U0001) 

For example, for ICU:

ivtestlib libivicu23.so 
05.30.0001 

NOTE: On Solaris, AIX, and Linux, the full path to the driver does not have to be specified for ddtestlib. The HP-UX version of ddtestlib, however, requires the full path.

getFileVersionString Function

Version string information can also be obtained programmatically through the function getFileVersionString. This function can be used when the application is not directly calling ODBC functions.

This function is defined as follows and is located in each driver's shared object:

const unsigned char* getFileVersionString(); 

This function is prototyped in the qesqlext.h file shipped with the product.