An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: scribes the issues resolved since general availability.  
• Third-party Components Compatibility Matrix: Provides the latest information about the third-party components installed with the product.  

Version 8.0.2

Enhancements

• The driver is upgraded to the 8.0 framework, thereby, ensuring that the base components stay aligned with the latest security fixes and enhancements.
• The driver is built using the CLIv2 library. The minimum CLIv2 library versions required for compatibility with the driver are as follows:
  • Windows - v17.20
  • Linux - v17.20
  • AIX - v17.20
  • Solaris - v16.20
  • HP - v16.20

Changed Behavior

• The trace library file names have been changed from ivtrc27.dll to ivtrc28.dll (32-bit) and from ddtrc27.dll to ddtrc28.dll (64-bit) to have the same file names across all platforms. This change allows for faster release of security updates and a more consistent user experience.
• The following operating systems are no longer supported:
  • AIX 32 Bit
  • Solaris.Sparc32

Notes, Known Issues, and Limitations

• When compiling an application on AIX for use with the driver for the Teradata database, you must use the -brtl option. For example:
  cc -o pgm pgm.o -brtl -lodbc
  or
  ld -o pgm -brtl pgm.o -lodbc
  
• The driver does not support specifying values for the same connection option multiple times in a connection string or DSN. If a value is specified using the same attribute multiple times or using both long and short attributes, the connection may fail or the driver may not behave as intended.
• All of the Release 8.0 Core Components (header files, etc.) needed for development of ODBC applications on UNIX and Linux are installed into the /include directory created by the product installer.
  Please read the notices.txt file in the installation directory for licensing information regarding the ODBC Core Components. Contact your Progress DataDirect representative if you have any questions.
  The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC Driver Manager can be used with any language that supports loading a C++ shared library; however, if you are using a programming language other than C++, you must take additional steps to ensure that the C++ libraries are initialized properly when loaded. If you are not using C++, consult your compiler documentation for instructions on using C++ shared libraries with your application.
  
• A default installation of the product on UNIX and Linux assumes that the value of the LANG environment setting is en_US. If your locale is not set to en_US, the drivers may not return error messages properly. In this case, you must create a symbolic link in the <Install_Dir>/locale directory that has the same value as the LANG environment setting. This link must point to the <Install_Dir>/locale/en_US directory.
• The column attributes 1001 and 1002, which were assigned as DataDirect-specific attributes, were inadvertently used as system attributes by the Microsoft 3.0 ODBC implementation. Applications using those attributes must now use 1901 and 1902, respectively.
• Because of inconsistencies in the ODBC specification, users attempting to use SQL_C_NUMERIC parameters must set the precision and scale values of the corresponding structure and the descriptor fields in the Application Parameter Descriptor.
• Some IBM AIX C compilers, such as xlc 3.1.4, do not support the use of C++ build binaries. C developers on AIX should consult their compiler documentation and verify that their AIX C compiler supports the use of C++ shared libraries or the application could be unstable.
• You may receive a 126 error when adding or configuring a data source stored on a network location. This is caused by the settings of the User Account Control (UAC) security feature on Windows 10. To work around this issue:
  Important: Implementing this fix disables security safeguards that are designed to protect your machine. Before starting, refer to the following Microsoft documentation for potential risks associated with disabling the UAC feature: http://windows.microsoft.com/en-us/windows/what-are-user-account-control-settings
  
  1. From the Start menu, type regedit in the search field; then, select regedit from the results list. The Registry Editor window opens.
  2. Navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. Right click on the subkey; then, select New > DWORD Value.
  4. Rename the new value EnableLinkedConnections.
  5. Right-click EnableLinkedConnections, and then click Modify. The Edit DWORD Value window opens.
  6. In the Value data field, type 1. Click OK.
  7. Close the Registry Editor; then, restart your computer.
• If you have installed an evaluation copy of the drivers and want to upgrade to a licensed version, you must use the Modify option of the installation program.
• When you first install a driver, you are given the option to install a default data source for that driver. We recommend that you install default data sources when you first install the drivers. If you do not install the default data source at this time, you will be unable to install a default data source for this driver later. To install a default data source for a driver after the initial installation, you must uninstall the driver and then reinstall it.
• The column attributes 1001 and 1002, which were assigned as DataDirect-specific attributes, were inadvertently used as system attributes by the Microsoft 3.0 ODBC implementation. Applications using those attributes must now use 1901 and 1902, respectively.
• Because of inconsistencies in the ODBC specification, users attempting to use SQL_C_NUMERIC parameters must set the precision and scale values of the corresponding structure and the descriptor fields in the Application Parameter Descriptor.
• One of the most common connectivity issues encountered while using IIS (Microsoft's Internet Information Server) concerns the use and settings of the account permissions. If you encounter problems using DataDirect drivers with an IIS server, refer to KnowledgeBase document number 4274 on the Progress DataDirect web site: http://knowledgebase.datadirect.com.

Version 7.1.6

Enhancements

• Some components of the driver are now compiled with a Visual Studio 2022 compiler for Windows platforms. As a result, you must have Microsoft Visual C/C++ runtime version 14.40.33810 or higher on your machine to run the driver.*
• For AIX platforms, the ICU library files that are installed with the product have been upgraded to version 74.1. As a part of this upgrade, the ICU library file names have changed. For the 32-bit driver, the ICU file name has changed from libivicu28.a to libivicu.a. For the 64-bit driver, the ICU file name has changed from libddicu28.a to libddicu.a. Notes:
• This upgrade does not apply to the other UNIX platforms.
• This upgrade is available starting in build 08.02.1072 of the ICU library files.
• libivicu27.a (32-bit) and libddicu27.a (64-bit) will continue to be included in the product package to support driver functionality.*

Changed Behavior

• The installer program now requires you to install a JRE that is Java SE 11 or higher before running the installer. In earlier versions, the JRE used by the installer program was included in the product. However, to avoid potential security vulnerabilities, the installer program no longer includes a JRE. Instead, the installer program uses the JRE in your environment to allow for the most secure version of a JRE to be used.

  Notes:

  • This change does not affect the JVM requirements for the driver. For the latest driver requirements, refer to the Product Compatibility Guide.
  • The installer program cannot remove the already installed JRE files from the install directory automatically. Remove them manually.

Version 7.1.5

No features introduced 

Version 7.1.4

No features introduced

Version 7.1.3

No features introduced

Version 7.1.2

No features introduced 

Version 7.1.1

No features introduced 

Version 7.1.0

No features introduced