What's New

OpenAccess SDK Release 8.1

Progress DataDirect OpenAccess SDK is the industry's leading custom driver development kit, enabling you to develop ODBC, JDBC, OLE DB, or ADO.NET drivers for any data source. Each new release of OpenAccess leverages DataDirect’s existing line of industry standard DataDirect Connect drivers, offering you significant upgrades and enterprise level features quickly.

Highlights of Release 8.1

This new release is focused on security and performance for ever-growing data sets, as well as enhancing the experience of the ADO.NET provider. Key highlights of this release include: 

OpenAccess SDK SQL Engine and IP SDK

  • Support for RIGHT OUTER JOIN operations
  • Improved support for nested join queries
  • Improved performance with indexed disk cache for nested query results
  • Improved calculation of precision of the scalar function result, based on precision of
    input arguments
  • Support for configurable behavior to enforce an integrity constraint check when null
    values are specified in non-nullable result columns with the IP_INFO_VALIDATE_NULL_CONSTRAINT ipGetinfo option
OpenAccess SDK Server
  • Support for service configurable option, ServiceNetworkBufferSize, to specify network
    protocol buffer size
  • Support for service configurable option, ServiceSSLVersions, to specify the version of
    cryptoprotocol to be used for encryption, when SSL is enabled
  • Upgrade of OpenSSL library to 1.0.2h
OpenAccess SDK Client for JDBC
  • Support for JDBC 4.0 specification
  • Support for the CryptoProtocolVersion connection option that specifies the version of the
    SSL standard used for encryption, whenever SSL is enabled
OpenAccess SDK Client for ODBC
  • Distribution of the sample Tableau TDC file with the OpenAccess ODBC client as a
    standard component
  • Support for the CryptoProtocolVersion connection option that specifies the version of the
    SSL standard that is used for encryption, whenever SSL is enabled
  • Upgrade of OpenSSL library to 1.0.2h
OpenAccess SDK Client for ADO.NET
  • Support for 64-bit row fetch
  • Support for public/global IP address for client identification
  • Support for the CryptoProtocolVersion connection option that specifies the version of the
    SSL standard that is used for encryption, whenever SSL is enabled
  • Inclusion of branding tool as part of installation
  • Support for Visual Studio 2013 and 2015
  • Dropped support for Visual Studio 2008 and 2010
  • Support for .NET Framework 4.5 and .NET Framework 4.6
  • Dropped support for .NET Framework 2.0, 3.0, 3.5, and 4.0

Release 5.3.1 Private Cloud

Progress® Rollbase® Version 5.3.1 Release Notes

Release Date 

December 12th, 2018


  • For information on supported platforms, see here.
  • For Third party acknowledgments, refer product documentation or the installation directory.

Fixed Issues


Following is the list of issues fixed with this release.
Case ID Defect ID Description
00470469 RB-9087 After Create Trigger on record created from Portal throws "You do not have permissions to view this record".
00470245 RB-9083 Modified Server API permissions and app with formula field in 4.5.x causes error when importing the App XML into 5.3.0.0
00466371 RB-9021 After upgrading to 5.3, all the portal pages display incorrect portal date format.
RB-9069 Session fixation issue and clear session on logout issue due to incorrect attributes in JSESSIONID.
RB-9074 When Rollbase is configured with Tomcat 9, change in tenant's localization settings is not updated.
RB-9041 databases.xml rewrites each time on every rollbase startup even without any change in the database details
RB-9040 Value changes within the shared property DefaultDateFormat are not picked up dynamically.

Known Issues


  1. On an existing Rollbase setups, in case if any user encounters "Error: no column assigned to Expression field Installation Expression" while updating records from Published Application, the workaround is to convert the expression field to 'formula' and then back to 'expression'. (This error should never occur in a fresh setup)
  2. MySQL Connector/J 8.0 is now recommended for MySQL 8.0. A notable change is that the driver’s class name has been changed from com.mysql.jdbc.Driver to com.mysql.cj.jdbc.Driver. With MySQL Connector/J 8.0, although the older class name is supported, it is advised to update the class name for existing databases.
  3. MySQL JDBC driver (8.0) drivers may affect Date/Time field values.  If any errors are encountered during Tomcat startup, please refer to this article. A date/time field may retain the current/correct date, but the time component might show a future time (such as 1:42 PM instead of the current time of 8:42 AM). The driver now expects an additional parameter ‘serverTimezone’ in the connection URL.
  4. Primary keys are now added to RB_RELATIONSHIP and RB_TRANSLATION tables. While executing the update_5.3.0.sql script if either or both of these tables contain any duplicate records, Duplicate entry / Primary Key Constraint Violation errors will be seen. To resolve such errors, please follow the approach detailed in article.
  5. For OpenEdge and Oracle databases, login names are now case insensitive. If more than one user with the same login name exists, regardless of case, the user may fail to login. In this event, the login name entries need to be fixed manually in the database. For other databases, the login name is already case insensitive.
  6. In REST APIs, newly introduced shared properties UseISODateFormatInRESTJSON and UseISODateFormatInRESTXMLQuery are enabled by default. As a result, Date, Date/Time fields (including Expression and Formula fields whose return type is Date or Date/Time) return the values in ISO format. To fallback to earlier behavior, these properties need to be disabled explicitly.


patch-whats-new

Read Next

What's new