SQL Drivers

DataFlex SQL Drivers from Data Access Worldwide

Version: 6.3.0.22

Release Date: May 5, 2021

Installation File: DataFlex SQL Drivers v.6.3.0.22.zip

Introduction

DataFlex SQL Drivers provide DataFlex Studio, Windows and Web Clients and WebApp Server with drivers that enable access to Microsoft SQL Server, IBM DB2 and ODBC databases, like MySQL, and other data sources. Use of DataFlex SQL Drivers is governed by the license agreement included with the Software Product with which the DataFlex SQL Drivers are installed. For licensing information, please contact Data Access Worldwide at sales@DataAccess.com or your Data Access Worldwide regional office or Channel Partner.

This ZIP file updates to the version shown above development environments that already have a previous version of the DataFlex SQL Drivers installed. It will also install drivers where no DataFlex SQL Drivers has been previously installed.

Do you need this driver version?

DataFlex installs DataFlex SQL Drivers as part of its installation, so you may already have the version of the drivers that you need. Please, check the list below to see if you need to update your drivers:

DataFlex 2019 - 19.1 (October 2019 release)  SQL Connectivity Kits version 6.3.0.15
DataFlex 2019 - 19.1 (April 2019 release)    SQL Connectivity Kits version 6.3.0.13
DataFlex 2017 - 19.0 (December 2017 release) SQL Connectivity Kits version 6.2.0.42
DataFlex 2017 - 19.0 (August 2017 release)   SQL Connectivity Kits version 6.2.0.40  

Because they include bug fixes and new features, as a general rule, we always recommend using the latest build of the drivers.

But you know your application and the details "under the hood" so you are the best person to determine when to perform the upgrade.

Upgrading Client Environments

The first thing to do is to consider if the current update is needed and then determine the right moment to install it.

If you determine that you are going to upgrade the drivers, you would always first upgrade them in the development environment for the DataFlex revision being used and fully test the application(s) you run in that host revision.

Once your applications have been thoroughly tested, deploy the applications with the new version of the driver and plan the upgrade of existing sites.

Keep in mind that this update is to be installed in development environments - the ZIP file includes files that are not needed in a client environment. In order to upgrade client sites, you will need to create your own installation and procedure following instructions outlined in the deployment book of the respective DataFlex Help System.

Product Registration

As any DataFlex products,  DataFlex SQL Drivers will need a valid license in order to be functional. The registration program and other aspects of Product Registration are explained in the online Help.

Recent Changes and Fixes (since Build 6.3.0.15)

The family of DataFlex SQL Drivers (including Microsoft SQL Server, IBM DB2 and ODBC) are published as a set. The changes and fixes listed in this document comprise a summary of changes made to that set. Some changes are specific to particular drivers and others are generic to the set.

Build 6.3.0.22
Changed the handling of binary data. Some database backends (MySQL) could not handle binary data properly. Binary data will now be read/written as pure binary.

Reduced size of DF_TEXT and DF_BINARY buffers below 16384. DF_TEXT and DF_BINARY columns with size below 16384 would still allocate buffers of 16384. Now changed to the actual column length as specified in the INT file.

ODBC_DRV:
PostgreSQL: Fix for handling binary data with PostgreSQL. PostgreSQL uses TYPEA type for binary data.
Changed PostgreSQL.int file.
PostgreSQL: Fix for handling descending index segments on PostgreSQL. Changed PostgreSQL.int file.
PostgreSQL: Fix max length for text columns. PostgreSQL ODBC driver returns 8190 as maximum length for text columns, while it can actually be 1GB.

MariaDB: Bugfix: Table with same name in multiple databases could use table definition from other database.
Bugfix: MariaDB EnumerateTables returns all tables across all databases.

PostgreSQL,Oracle,MySQL,MariaDB: Implemented identity column support for PostgreSQL and Oracle. Improved auto_increment support for MySQL and MariaDB.

PostgreSQL: Use_Identity_Type setting in PostgreSQL.Int is true by default.
This will create identity columns with the GENERATED BY DEFAULT AS IDENTITY clause. This clause is supported in PostgreSQL 10 and later. For earlier PostgreSQL versions set Use_Identity_Type 0
Changed PostgreSQL.int

Oracle: Use_Identity_Type setting in Oracle.Int is true by default.
This will create identity columns with the GENERATED BY DEFAULT AS IDENTITY clause. This clause is supported in Oracle 12c and later. For earlier Oracle versions set Use_Identity_Type 0
Changed Oracle.int

MySQL/MariaDB: Improved auto_increment support for MySQl/MariaDB.
Recnum tables will now have GENERATE_RECORD_ID_METHOD IDENTITY_COLUMN in the table INT file. Changed MySQL.INT and MariaDB.int.

Build 6.3.0.21
Bugfix: After moving a value to a field buffer that already contained that same value, the DF_FILE_CHANGED attribute would sometimes incorrectly be set to true.

Build 6.3.0.20
Bugfix: SQLSetParameter could cause right truncation or function sequence errors.

Build 6.3.0.19
ODBC_DRV:
PostgreSQL: citext type was returned as DF_ASCII(255), changed to DF_TEXT.

Build 6.3.0.18
SQLFetchResultsetValues will no longer generate "Invalid Cursor State" error for non-existing result set.
Changed sql.pkg

Build 6.3.0.17
Constrained_find would in some situations invalidate the Find Cache on every find, causing slow performance.

Build 6.3.0.16
Internal build.

Installing DataFlex SQL Drivers

Before installing this version of the DataFlex SQL Drivers in your production environment, make sure you:
+ review the documentation installed both in the Documentation and Help folder (see items 2 and 3 under ZIP File Contents) to learn about the changes that this version will bring to your environment
+ install it in a test environment first to verify the effects this new version has on your existing applications

Once ready, install the new build by following the steps listed below:
1. Stop WebApp Server service, and exit any DataFlex tools or applications so files that need to be replaced are not in use

2. Backup your current DataFlex environment making sure to include the five folders listed above that will be receiving the new files

3. Download the ZIP to a local folder

4. Extract the contents of the ZIP file to the DataFlex root folder where you would like to update/use the DataFlex SQL Drivers version 6.3.0.22. For example, if you would like to install this update to be used in a DataFlex 19.1 Studio environment, choose to extract DataFlex SQL Drivers v.6.3.0.22.zip to the root folder of 19.1 (default location: C:\Program Files\DataFlex 19.1) - the files will be extracted to the same destination subfolders as listed in the zip. If asked, choose to overwrite and replace files in the destination folders

Important!
If you are using the Windows built-in ability to deal with compressed files and have installed DataFlex into the default location (i.e. under Program Files), when extracting the contents of the ZIP file you may be prompted to use elevated rights in case you are not logged in as Administrator.

However, if you are using a third-party tool (like WinZip), you may NOT be prompted to use elevated rights and the extraction may silently just not work. Please, follow the third-party tool manufacturer’s instructions on how to extract files when elevated rights is needed.

Support

Data Access Worldwide offers no specific support for this installation process.

Support for DataFlex SQL Drivers will be included with your DataFlex license and will follow current support policies outlined on the company's website at https://www.dataaccess.com/Support.

If you have any questions, email support@DataAccess.com.

Copyright 2021, Data Access Corporation.

SQL Connectivity Kits

DataFlex SQL Connectivity Kits from Data Access Worldwide

Version: 6.3.0.15

Release Date: October 30, 2019

Introduction

Connectivity Kits provide DataFlex Studio, Windows and Web Clients and WebApp Server with database drivers for Microsoft SQL Server, IBM DB2 and via ODBC MySQL and other database servers and data sources. Use of Connectivity Kits is governed by the license agreement included with the Software Product with which the Connectivity Kits are installed. For licensing information, please contact Data Access Worldwide at sales@DataAccess.com or your Data Access Worldwide regional office or Channel Partner.

This ZIP file updates to the version shown above development environments that already have a previous version of the Connectivity Kits installed. It will also install drivers where no Connectivity Kit has been previously installed.

Online Documentation

SQL Drivers

The features, issues and additional capabilities of using the DataFlex SQL Drivers are discussed in the Data Connectivity section of the online Help.

Product Registration

As any DataFlex products,  DataFlex SQL Drivers will need a valid license in order to be functional. The registration program and other aspects of Product Registration are explained in the online Help.

Recent Changes and Fixes (since Build 6.3.0.13)

The family of SQL Connectivity Kits (including Microsoft SQL Server, IBM DB2 and ODBC) are published as a set. The changes and fixes listed in this document comprise a summary of changes made to that set. Some changes are specific to particular CKs and others are generic to the set.

Build 6.3.0.15

Conversion of system table would fail if the source table was SQL driver based.

Build 6.3.0.14

SQLSetParameter would add a trailing space to the passed parameter.

Odbc_drv:

MySQL: Creation or conversion of Numeric(14.8) columns would fail with Syntax error.

MySQL: Creation or conversion of DF_ASCII with length > 255 would fail. Such columns will now be converted to DF_TEXT, since MySQL char and varchar are limited to length 255.

Build 6.3.0.13

Odbc_drv:

MySQL: Refresh table in DataFlex Studio would fail with “Could not open and analyze SQL table or its INT file” error. Caused by schema name being set to login user name.

MariaDB: Refresh table would sometimes write incorrect primary index to INT file.

For full details and a complete list of changes since build 4.0.0.35, please refer to SQL Connectivity Changes and Fixes.pdf available in the ZIP file in the Documentation folder.

Supported Environments

DataFlex 18.x and higher

• Microsoft SQL Server 2017 (including LocalDB) using ODBC Driver 17 for SQL Server (or higher)
• Microsoft SQL Server 2016 (including LocalDB) using ODBC Driver 13.1 for SQL Server (or higher)
• Microsoft SQL Server 2014 (including LocalDB) using ODBC Driver 11 or 13 for SQL Server (or higher)
• Microsoft SQL Server 2012 (SP2 including LocalDB) using SQL Server 2012 Native Client (v.11.0 or higher)

DB2 10.1 and higher

MySQL 8.0.17 (or later) and compatibles using MySQL Connector/ODBC 8.0.17 (or later)
MDAC 2.8

Windows 7 and higher

Support

Data Access Worldwide offers no specific support for this installation process.

Support for Connectivity Kits will be included with your DataFlex license and will follow current support policies outlined on the company’s website at http://www.dataaccess.com/resources/customer-support-1196.

If you have any questions, email support@DataAccess.com.

Copyright 2019, Data Access Corporation.

SQL Connectivity Kits

DataFlex SQL Connectivity Kits from Data Access Worldwide

Current Version: 6.3.0.13

Release Date: April 10, 2019

Installation File: SQL Connectivity Kits v.6.3.0.13.zip

Introduction

Connectivity Kits provide DataFlex Studio, Windows and Web Clients and WebApp Server with database drivers for Microsoft SQL Server, IBM DB2 and via ODBC MySQL and other database servers and data sources.

Use of Connectivity Kits is governed by the license agreement included with the Software Product with which the Connectivity Kits are installed. For licensing information, please contact Data Access Worldwide at sales@DataAccess.com or your Data Access Worldwide regional office or Channel Partner.

This ZIP file updates to the version shown above development environments that already have a previous version of the Connectivity Kits installed. It will also install drivers where no Connectivity Kit has been previously installed.

Online Documentation

SQL Drivers

The features, issues and additional capabilities of using the DataFlex SQL Drivers are discussed in the Data Connectivity section of the online Help.

Product Registration

As any DataFlex products,  DataFlex SQL Drivers will need a valid license in order to be functional. The registration program and other aspects of Product Registration are explained in the online Help.

Upgrading Client Environments

The first thing to do is to consider if the current update is needed and then determine the right moment to install it.

If you determine that you are going to upgrade the drivers, you would always first upgrade them in the development environment for the DataFlex revision being used and fully test the application(s) you run in that host revision.

Once your applications have been thoroughly tested, deploy the applications with the new version of the driver and plan the upgrade of existing sites.

Keep in mind that this update is to be installed in development environments - this ZIP file includes files that are not needed in a client environment. In order to upgrade client sites, you will need to create your own installation and procedure following instructions outlined in the deployment book of the respective DataFlex Help System.

Recent Changes and Fixes (since Build 6.2.0.42)

The family of SQL Connectivity Kits (including Microsoft SQL Server, IBM DB2 and ODBC) are published as a set. The changes and fixes listed in this document comprise a summary of changes made to that set. Some changes are specific to particular CKs and others are generic to the set.

For details on those changes, please refer to SQL Connectivity Recent Changes and Fixes.pdf

Build 6.3.0.13

Odbc_drv:

MySQL: Refresh table in DataFlex Studio would fail with “Could not open and analyze SQL table or its INT file” error. Caused by schema name being set to login user name.

MariaDB: Refresh table would sometimes write incorrect primary index to INT file.

Build 6.3.0.12

Odbc_drv:

Prior DataFlex ODBC drivers had several issues that caused some functionality not to work when used with MySQL and MariaDB. Several changes have been made in this update to make the DataFlex ODBC driver work properly with these databases.

Build 6.3.0.11

All DataFlex SQL Drivers:

Passing a variable length parameter (e.g varchar(max) ) for a stored procedure with SQLSetParameter could in some circumstances cause an exception.

When receiving result messages from a stored procedure or SQL script with SQLGetMessage, messages would be limited to 512 characters. The maximum length for result messages has been increased to 1024.

Build 6.3.0.10

All DataFlex SQL Drivers:

Embedded SQL. Changed SQL.pkg.

Added support to change the cursor type for an embedded SQL statement.

By using a different cursor type, it is no longer necessary to have variable length columns (varchar(max), varbinary(max)) last in the Select statement.

New embedded SQL function: Procedure SQLSetStmtAttribute Integer iAttribId String sAttribValue

Function SQLGetStmtAttribute Integer iAttribId Returns String replaces SQLStmtAttribute function (now obsolete).

Build 6.3.0.9

All DataFlex SQL Drivers:

Additional changes for parameterized queries. Changed sql.pkg

Further details and examples see below at Embedded SQL Parameterized queries

Mssqldrv:

Mssqldrv.int: Changed comments to reflect type mappings for SQL Server 2012 also apply for SQL Server 2014, SQL Server 2016 and SQL Server 2017.

Build 6.3.0.8

All DataFlex SQL Drivers:

Added support for parameterized queries in embedded SQL.

New sql.pkg with new functions:

SQLSetParameter

SQLSetNextParameter.

Further details and examples see Embedded SQL Parameterized queries

Build 6.3.0.7

DB2_DRV:

On a DB2 standard table with an identity column: Would generate "Wrong number of parameters." error when a value was provided for the identity column.

After restructure of DB2 standard table with an identity column, the identity value would not properly be restarted.

Build 6.3.0.6

MSSQLDRV:

Added Function SqlServerClientDriverName that returns the driver name. The driver name can be used to compose a connect string.

Changed mssqldrv.pkg

All DataFlex SQL Drivers:

Moved Function DriverIndex from mssqldrv.pkg (Class cMSSQLHandler) to cli.pkg (Class cCLIHandler)

Changed cli.pkg and mssqldrv.pkg

Changed DF_FILE_DATABASE_ID to make consistent with DF_DATABASE_ID.

Build 6.3.0.5

All DataFlex SQL Drivers:

Embedded SQL: Changed driver internal handling of connection and statement handles.

Odbc_drv:

Removed obsolete ODBC commands from odbc_drv.pkg.

Build 6.3.0.4

All DataFlex SQL Drivers:

Cleanup of driver related pkgs - Sql.pkg (changed single line if’s to multiline)

Changed driver internal handling of DF_DATABASE_ID attribute.

Added compiler warning DFERR_COMP_WARNING_OBSOLETE_CMD for obsolete commands

MSSQLDRV:

Added support for “ODBC driver 17 for SQL Server”. (SQL Server 2017 client)

Changed Mssqldrv.pkg

DB2_DRV:

For the DB2 TIMESTAMP type (DataFlex DATETIME type) the number of decimals (milliseconds, nanoseconds) can now be specified. DB2 allows TIMESTAMP(0) thru TIMESTAMP(12). Default is 0 decimals.

In the DataFlex Studio this can be specified as length 23.0 thru 23.12.

Note that more than 3 decimals may be truncated by the DataFlex runtime. It is recommended to use a maximum of 3 decimals for DATETIME type.

Earlier versions of DataFlex DB2 driver would create DATETIME columns as TIMESTAMP(6).

Changed DB2_DRV_DriverDef.xml file.

Build 6.3.0.3

All DataFlex SQL Drivers:

Cleanup of driver related pkgs: cli.pkg mssqldrv.pkg db2_drv.pkg odbc_drv.pkg sql.pkg

Embedded SQL function SQLColAttribute SQLCOLATTRIB_DFTYPE returned invalid values for some native types

Fill_Field DF_LOW/DF_HIGH of a time column, filled with incorrect time values. This caused "Time contains an invalid value." errors. Also during constrained finds on indexes with time column.

After changing Index Type from Server to Client_Only AND clearing the Index Name, the table could not be opened

anymore because of invalid INT file.

Exclusive open of a table with no index.1 would cause ’Index number out of range’ error.

ODBC_DRV:

Creating indexes and primary keys on PostgreSQL failed when using other than default schema ’public’.

Structure_End would lowercase schema names on PostgreSQL

Build 6.3.0.2

All DataFlex SQL Drivers:

Removed DF_File_Record_Identity attribute from Studio driver configuration files.

Fix to make Studio driver configuration files work with DataFlex Studio before 19.0.

Changed files:

MSSQLDRV_DriverDef.xml

DB2_DRV_DriverDef.xml

ODBC_DRV_Driverdef.xml.

Build 6.3.0.1

All DataFlex SQL Drivers:

Delete_Index of a non-temporary index outside structure_start/structure_end caused access violation. (BT 7318)

Recnum tables with RECNUM column bigint could not be restructured. Fixed.

Build 6.2.0.42

All DataFlex SQL Drivers: Removed DF_File_Record_Identity attribute from Studio driver configuration files.

Fix to make Studio driver configuration files work with DataFlex Studio before 19.0.

For full details and a complete list of changes since build 4.0.0.35, please refer to SQL Connectivity Changes and Fixes.pdf available in the ZIP file in the Documentation folder.

Supported Environments

DataFlex 18.x and higher

DB2 10.1 and higher

MDAC 2.8

Windows 7 and higher

ZIP File Contents

The ZIP file includes 5 folders containing the following files:

1. Bin

2. Documentation

SQL Connectivity Recent Changes and Fixes.pdf

Whats New in SQL Connectivity Version 6.pdf

3. Help

SQL_Connectivity_Kits.htm

4. Pkg

5. Usr

DFErr003.dat

DFErr003.hdr

DFErr003.tag

Support

Data Access Worldwide offers no specific support for this installation process.

Support for Connectivity Kits will be included with your DataFlex license and will follow current support policies outlined on the company’s website at http://www.dataaccess.com/resources/customer-support-1196.

If you have any questions, email support@DataAccess.com.

Copyright 2019, Data Access Corporation.

DataFlex SQL Connectivity Kits from Data Access Worldwide Version: 6.2.0.42 Release Date: December 5, 2017
File: SQL Connectivity Kits v.6.2.0.42.zip

Connectivity Kits provide DataFlex Studio, Windows and Web Clients and WebApp Server with database drivers for Microsoft SQL Server, IBM DB2 and via ODBC MySQL and other database servers and data sources. Use of Connectivity Kits is governed by the license agreement included with the Software Product with which the Connectivity Kits are installed. For licensing information, please contact Data Access Worldwide at sales@DataAccess.com or your Data Access Worldwide regional office or Channel Partner. This ZIP file updates to the version shown above deployment environments that already have a previous version of the Connectivity Kits installed. It will also install drivers where no Connectivity Kit has been previously installed.

Do you need this driver version? 

DataFlex installs SQL Connectivity Kits as part of its installation, so you may already have the version of the drivers you need. Please, check the list below to see if you need to update your drivers: DataFlex 2017 - 19.0: SQL Connectivity Kits version 6.2.0.42 DataFlex 2016 - 18.2: SQL Connectivity Kits version 6.1.0.27 DataFlex 2015 - 18.1: SQL Connectivity Kits version 6.1.0.18

Recent Changes and Fixes (since Build 6.1.0.32) 

The family of SQL Connectivity Kits (including Microsoft SQL Server, IBM DB2 and ODBC) are published as a set. The changes and fixes listed in this document comprise a summary of changes made to that set. Some changes are specific to particular CKs and others are generic to the set. For details on those changes, please refer to SQL Connectivity Recent Changes and Fixes.pdf

Build 6.2.0.42 All DataFlex SQL Drivers: Removed DF_File_Record_Identity attribute from Studio driver configuration files. Fix to make Studio driver configuration files work with DataFlex Studio before 19.0.

Build 6.2.0.41 All DataFlex SQL Drivers: Delete_Index of a non-temporary index outside structure_start/structure_end caused access violation. (BT 7318) Recnum tables with RECNUM column bigint could not be restructured. Fixed. System table with real recnum column on SQL and no primary_index 0 in the INT file, would not hide the recnum column. MSSQLDRV: Changed MSSQLDRV_DriverDef.xml. MSSQLDRV_DriverDef.xml would only work with DataFlex Studio 19.0, but not with DataFlex Studio’s before 19.0.

Build 6.2.0.40 MSSQLDRV: A date or datetime column with a default value ’getdate()’ would not be filled with the current datetime on save of a new record. DB2_DRV and ODBC_DRV: A date or datetime column with a default value ’CURRENT_TIMESTAMP’ would not be filled with the current datetime on save of a new record. The default value to generate a timestamp can vary per database backend.

Build 6.2.0.39 All DataFlex SQL Drivers: Set_attribute DF_INDEX_NAME for a temporary index caused exception. Changed cli.pkg DF_INDEX_TEMPORARY had wrong value.

Build 6.2.0.38 MSSQLDRV: In some very rare situations a system table can unintentionally end up with more than 1 record. On SQL Server this would generate very hard to track-down errors: “Connection is busy with results for another command”. Made a change that prevents the connection busy error. Instead, a “System Table has more than one record.” error will be generated on open.

Build 6.2.0.37 All DataFlex SQL Drivers: Changed naming in driver dll properties: mssqldrv.dll DataFlex SQL Server Driver db2_drv.dll DataFlex DB2 Driver odbc_drv.dll DataFlex ODBC driver

Build 6.2.0.36 MSSQLDRV: When using GUID (uniqueidentifier) columns with default value newid() or newsequentialid(), the OUTPUT clause is used to return generated GUID values in the buffer. When the table also has a trigger defined, this caused an error about invalid use of the OUTPUT clause. Changed to use OUTPUT INTO clause.

Build 6.2.0.35 All CLI Connectivity Kits: Updated Studio driver configuration files

Build 6.2.0.34 All CLI Connectivity Kits: Changed index creation order during restructure/conversion All CLI Connectivity Kits Improved context information in Open errors. Added Table= and Source= context.

Build 6.2.0.33 DB2_DRV: When calling a DB2 stored procedure with a CLOB argument the length of the passed parameter in SQLSetArgument was larger than 16K. The parameter would be truncated to 16K.

Build 6.2.0.32 All CLI Connectivity Kits: Changed some error texts for open errors.

Build 6.2.0.31 All CLI Connectivity Kits: Open of a system table in database explorer 19.0 raised "Index number out of range" error. Caused by Get_attribute DF_INDEX_NAME of a system table raising "Index number out of range" error. Changed to not generate error but return empty string for DF_INDEX_NAME.

Build 6.2.0.30 All CLI Connectivity Kits: When setting or getting a SQL filter no oem/ansi conversion was done caused SQL filters not to work properly with accented characters. MSSQLDRV: Added SQL Server client name in error text on minimum client version.

Build 6.2.0.29 All CLI Connectivity Kits: Changed cli.pkg to add constants for missing cli error codes (CLIERR_ ) Added version check for minimum database client version for DB2_DRV and ODBC_DRV. New driver configuration file (mssqldrv.int, db2_drv.int, odbc_drv.int) keyword: MINIMUM_CLIENT_VERSION New attribute: DF_DRIVER_MINIMUM_CLIENT_VERSION DB2_DRV: Made a change to enable DSN-less connections for DB2. All CLI Connectivity Kits: Changed driver configuration files (mssqldrv.int, db2_drv.int, odbc_drv.int) to add new settings for Connectivity Kits 6.2: Minimum_Client_Version, Login_On_Open and Allowed_structure_changes

Build 6.2.0.28 All CLI Connectivity Kits: All searches for connectstring keywords (like SERVER, DSN) made case insensitive. MSSQLDRV: Added version check for minimum database client version. New driver configuration file (mssqldrv.int) keyword: MINIMUM_CLIENT_VERSION New attribute: DF_DRIVER_MINIMUM_CLIENT_VERSION The default value for minimum client version is 10 SQL Server Native Client 10.0 (SQL Server 2008 client) The version check will be performed during login. Note the first open in a program may also do a login. MSSQLDRV: Changed mssqldrv.pkg to add Function SqlServerClientVersionName Integer iClientVersion Returns String ODBC_DRV: Changed ODBC_DRV_DriverDef.xml to include new attributes for DataFlex 19.0 / Connectivity Kit 6.2: df_file_restructure df_file_restructure_int_only df_file_allowed_structure_changes df_index_sql_type df_index_number

Build 6.2.0.27 Internal build

Build 6.2.0.26 DB2_DRV and ODBC_DRV: Enumeration of tables with function EnumerateTables would not list all tables when one or more tables with comments longer than 128 characters were found.

Build 6.2.0.25 All CLI Connectivity Kits: Reference to index.0 was not written to the INT file in case of an index-only restructure. (A restructure that only involves creating/dropping of indexes). All CLI Connectivity Kits: If no SERVER_NAME was present in the INT file, would cause an exception.

Build 6.2.0.24 All CLI Connectivity Kits: cli.pkg Removed double ifdef All CLI Connectivity Kits: After a failed login with invalid connection id, a connection handle was not released.

Build 6.2.0.23 Internal build

Build 6.2.0.22 MSSQLDRV: Changed mssqldrv.pkg to add constants for “ODBC Driver 11 for SQL Server” (Client for SQL Server 2014) and “ODBC Driver 13 for SQL Server”. (Client for SQL Server 2016) in mssqldrv.pkg. Added new function EnumerateServersLocal.

Build 6.2.0.21 Internal build

Build 6.2.0.20 MSSQLDRV: Added support for “ODBC Driver 11 for SQL Server” (Client for SQL Server 2014) and “ODBC Driver 13 for SQL Server”. (Client for SQL Server 2016). The MSSQLDRV connectivity Kit will now recognize a range of clients that includes ODBC Driver 13 for SQL Server. All CLI Connectivity Kits: Bug in RedirectIdConnectString caused memory error in logout. All CLI Connectivity Kits: Setting a constrain with accented characters did no oem/ansi translation. MSSQLDRV: Changed default map schema for SQL Server (DEFAULT_MAP_DF_TO_SQL_TYPE_SCHEMA) to MAP_DF_TO_SQL_TYPE_SQL2012. Build 6.2.0.19 All CLI Connectivity Kits: A masked time value of 00:00:00 would be passed as " : : ", causing a “Time contains an invalid value” error. This will now be handled as time value 00:00:00.

Build 6.2.0.19 All CLI Connectivity Kits: Restructure prevention changes. Implemented a new table level attribute DF_FILE_ALLOWED_STRUCTURE_CHANGES

Build 6.2.0.18 All CLI Connectivity Kits: Added new DF_DRIVER_CONFORMANCE level bit All CLI Connectivity Kits: Implemented a new setting ALLOWED_STRUCTURE_CHANGES

Build 6.2.0.17 All CLI Connectivity Kits: If an error occurs during open, the driver will now return error 75 DFERR_CANT_OPEN_DATA_FILE.

Build 6.2.0.16 All CLI Connectivity Kits: Bugfix: Setting the value of a SQL_TIME column, could cause memory overwrite. RedirectIdConnectString and RedirectIdConnectStringKeepLoggedIn now combined to single function with bKeepLoggedIn parameter. New RedirectIdConnectString function.

Build 6.2.0.15 New RedirectIdConnectStringKeepLoggedIn function. Amended version of RedirectIdConnectString function.

Build 6.2.0.14 Added new attribute DF_DATABASE_DEFAULT_DATABASE. New RedirectIdConnectString function. MSSQLDRV: Bugfix conversion to SQL Server - CLI_BCP function. When date columns allow nulls (Default_Nullable_Date setting in mssqldrv.int) and no dummy zero dates are used (Default_Use_Dummy_Zero_Date in mssqldrv.int) the conversion will now save 0 dates as NULL in SQL Server.

Build 6.2.0.13 All CLI Connectivity Kits: Setting the DD value of a text column could cause memory error All CLI Connectivity Kits: Moving data to a df_ascii/sql_varchar column, where the data was larger than the field length, could cause a memory error.

Build 6.2.0.12 Added new embedded SQL function SQLConnectionConnect

Build 6.2.0.11 All CLI Connectivity Kits: Trying to open a table that does not exist in the SQL database, an "Invalid cursor state" error would be raised. Now changed to "Table not in connection" error. All CLI Connectivity Kits: Added new driver level setting LOGIN_ON_OPEN and new driver level attribute DF_DRIVER_LOGIN_ON_OPEN New cli.pkg with DF_LOGON_ON_OPEN attribute added.

Build 6.2.0.10 ODBC_DRV: Oracle columns created as type INTEGER returned an incorrect length. All CLI Connectivity Kits: Changing DF_Length of integer type columns is now an int file only change (df_file_restructure_int_only). All CLI Connectivity Kits: When renumbering an index (DF_INDEX_NUMBER) that is the primary index, the df_file_primary_index must also be renumbered.

Build 6.2.0.9 Support for temporary indexes that are created on the fly at runtime. They will only exist as long as the table is open. Temporary indexes will not be created on the server. New cli.pkg: Added DF_INDEX_TEMPORARY as possible value for DF_INDEX_SQL_TYPE attribute.

Build 6.2.0.8 Fixed a bug where create_index did not adjust last_index_number properly

Build 6.2.0.7 Bugfix: SQLConnect crashed when connecting with a not existing connection ID. Bugfix: Opening table with no index definition in INT (system table !) crashed the driver.

Build 6.2.0.6 If a column appears as a segment in a server_only index, the field_index of the column will no longer be set during open. When adding a new index (Create_Index) and there are server_only indexes present, the new index will get the number of the first server_only index. The server_only index(es) will get their index number incremented, so they remain at the end of the index list. Added new attribute DF_INDEX_NUMBER that allows to renumber indexes. New cli.pkg with DF_INDEX_NUMBER added New MSSQLDRV_DriverDef.xml with DF_INDEX_NUMBER added

Build 6.2.0.5 New attribute DF_FILE_RESTRUCTURE_INT_ONLY added. New cli.pkg with DF_FILE_RESTRUCTURE_INT_ONLY attribute added.

Build 6.2.0.4 New index attribute DF_INDEX_SQL_TYPE added. This attribute replaces DF_INDEX_ON_BACKEND attribute. DF_INDEX_ON_BACKEND remains as a read-only attribute for backward compatibility, but should no longer be used. New MSSQLDRV_DriverDef.xml file - added DF_INDEX_SQL_TYPE attribute. New cli.pkg - added DF_INDEX_SQL_TYPE attribute.

Build 6.2.0.3 All CLI Connectivity Kits: During conversion recnum index would be created as client side index.

Build 6.2.0.2 All CLI Connectivity Kits: The default for DF_INDEX_ON_BACKEND was false when creating new index on new table. This caused all indexes to be created as client side indexes during conversion.

Build 6.2.0.2 (merge from 6.1.0.28) All CLI Connectivity Kits: On a standard table with an identity column (df_file_identity = true), when inserting or deleting a column BEFORE the identity column, the identity would not be adjusted. This caused identity insert error during restructure.

Build 6.2.0.1 Improved support for client side indexes. Attribute DF_INDEX_ON_BACKEND is now a read/write attribute.

For full details and a complete list of changes since build 4.0.0.35, please refer to SQL Connectivity Changes and Fixes.pdf available in the ZIP file in the Documentation folder.

Supported Environments 

• DataFlex 18.x and higher
• Microsoft SQL Server 2017 (including LocalDB) using ODBC Driver 13.1 for SQL Server
• Microsoft SQL Server 2016 (including LocalDB) using ODBC Driver 13 for SQL Server
• Microsoft SQL Server 2014 (including LocalDB) using ODBC Driver 11 for SQL Server
• Microsoft SQL Server 2012 (SP3 including LocalDB) using SQL Native Client 11.0
  DB2 10.1 and higher MDAC 2.8
• Windows 7 and higher

ZIP File Contents 

The ZIP file includes five folders containing the following files:
1. Bin Access.int CKDaemon.exe DB1398.dfr DB2_Drv.cfg db2_drv.dll db2_drv.int DB2_DRV_DriverDef.xml DB2rtx.dll MS1383.dfr MSSQLDrv.cfg mssqldrv.dll mssqldrv.int MSSQLDRV_DriverDef.xml MSSQLrtx.dll MySQL.int OD1476.dfr ODBC_Drv.cfg odbc_drv.dll odbc_drv.int ODBC_Drv_Database.int ODBC_DRV_DriverDef.xml ODBCrtx.dll ora_drv_DriverDef.xml Oracle.int Pervasive.SQL.int PostgreSQL.int Register.exe Register.exe.manifest winsetup.dll
2. Documentation SQL Connectivity Recent Changes and Fixes.pdf Whats New in SQL Connectivity Version 6.pdf
3. Help Connectivity.chm
4. Pkg cli.pkg cTableColumnFetchHelper.pkg db2_drv.pkg dir.txt MSSqldrv.pkg odbc_drv.pkg sql.pkg sqlOld.pkg
5. Usr DFErr003.dat DFErr003.hdr DFErr003.tag

Installing SQL Connectivity Kits

Before installing this version of the Connectivity Kit in your production environment, make sure you: + review the documentation installed both in the Documentation and Help folder (see items 2 and 3 under ZIP File Contents) to learn about the changes that this version will bring to your environment + install it in a test environment first to verify the effects this new version has on your existing applications Once ready, install the new build by following the steps listed below:
1. Exit any DataFlex tools or applications so files that need to be replaced are not in use
2. Backup your current DataFlex environment making sure to include the five folders listed above that will be receiving the new files
3. Download the ZIP to a local folder
4. Extract the contents of the ZIP file to the DataFlex root folder where you would like to update/use the Connectivity Kits version 6.2.0.42. For example, if you would like to install this update to be used in a DataFlex 18.0 Studio environment, choose to extract SQL Connectivity Kits v.6.2.0.42.zip to the root folder of 18.0 (default location: C:\Program Files\DataFlex 18.0) - the files will be extracted to the same destination subfolders as listed in the zip. If asked

DataFlex SQL Connectivity Kits from Data Access Worldwide Version: 6.2.0.40 Release Date: December 5, 2017
File: SQL Connectivity Kits v.6.2.0.40.zip

Connectivity Kits provide DataFlex Studio, Windows and Web Clients and WebApp Server with database drivers for Microsoft SQL Server, IBM DB2 and via ODBC MySQL and other database servers and data sources. Use of Connectivity Kits is governed by the license agreement included with the Software Product with which the Connectivity Kits are installed. For licensing information, please contact Data Access Worldwide at sales@DataAccess.com or your Data Access Worldwide regional office or Channel Partner. This ZIP file updates to the version shown above deployment environments that already have a previous version of the Connectivity Kits installed. It will also install drivers where no Connectivity Kit has been previously installed.

Do you need this driver version? 

DataFlex installs SQL Connectivity Kits as part of its installation, so you may already have the version of the drivers you need. Please, check the list below to see if you need to update your drivers: DataFlex 2017 - 19.0: SQL Connectivity Kits version 6.2.0.42 DataFlex 2016 - 18.2: SQL Connectivity Kits version 6.1.0.27 DataFlex 2015 - 18.1: SQL Connectivity Kits version 6.1.0.18

Recent Changes and Fixes (since Build 6.1.0.32) 

The family of SQL Connectivity Kits (including Microsoft SQL Server, IBM DB2 and ODBC) are published as a set. The changes and fixes listed in this document comprise a summary of changes made to that set. Some changes are specific to particular CKs and others are generic to the set. For details on those changes, please refer to SQL Connectivity Recent Changes and Fixes.pdf

MSSQLDRV: A date or datetime column with a default value ’getdate()’ would not be filled with the current datetime on save of a new record. DB2_DRV and ODBC_DRV: A date or datetime column with a default value ’CURRENT_TIMESTAMP’ would not be filled with the current datetime on save of a new record. The default value to generate a timestamp can vary per database backend.

Build 6.2.0.39 All DataFlex SQL Drivers: Set_attribute DF_INDEX_NAME for a temporary index caused exception. Changed cli.pkg DF_INDEX_TEMPORARY had wrong value.

Build 6.2.0.38 MSSQLDRV: In some very rare situations a system table can unintentionally end up with more than 1 record. On SQL Server this would generate very hard to track-down errors: “Connection is busy with results for another command”. Made a change that prevents the connection busy error. Instead, a “System Table has more than one record.” error will be generated on open.

Build 6.2.0.37 All DataFlex SQL Drivers: Changed naming in driver dll properties: mssqldrv.dll DataFlex SQL Server Driver db2_drv.dll DataFlex DB2 Driver odbc_drv.dll DataFlex ODBC driver

Build 6.2.0.36 MSSQLDRV: When using GUID (uniqueidentifier) columns with default value newid() or newsequentialid(), the OUTPUT clause is used to return generated GUID values in the buffer. When the table also has a trigger defined, this caused an error about invalid use of the OUTPUT clause. Changed to use OUTPUT INTO clause.

Build 6.2.0.35 All CLI Connectivity Kits: Updated Studio driver configuration files

Build 6.2.0.34 All CLI Connectivity Kits: Changed index creation order during restructure/conversion All CLI Connectivity Kits Improved context information in Open errors. Added Table= and Source= context.

Build 6.2.0.33 DB2_DRV: When calling a DB2 stored procedure with a CLOB argument the length of the passed parameter in SQLSetArgument was larger than 16K. The parameter would be truncated to 16K.

Build 6.2.0.32 All CLI Connectivity Kits: Changed some error texts for open errors.

Build 6.2.0.31 All CLI Connectivity Kits: Open of a system table in database explorer 19.0 raised "Index number out of range" error. Caused by Get_attribute DF_INDEX_NAME of a system table raising "Index number out of range" error. Changed to not generate error but return empty string for DF_INDEX_NAME.

Build 6.2.0.30 All CLI Connectivity Kits: When setting or getting a SQL filter no oem/ansi conversion was done caused SQL filters not to work properly with accented characters. MSSQLDRV: Added SQL Server client name in error text on minimum client version.

Build 6.2.0.29 All CLI Connectivity Kits: Changed cli.pkg to add constants for missing cli error codes (CLIERR_ ) Added version check for minimum database client version for DB2_DRV and ODBC_DRV. New driver configuration file (mssqldrv.int, db2_drv.int, odbc_drv.int) keyword: MINIMUM_CLIENT_VERSION New attribute: DF_DRIVER_MINIMUM_CLIENT_VERSION DB2_DRV: Made a change to enable DSN-less connections for DB2. All CLI Connectivity Kits: Changed driver configuration files (mssqldrv.int, db2_drv.int, odbc_drv.int) to add new settings for Connectivity Kits 6.2: Minimum_Client_Version, Login_On_Open and Allowed_structure_changes

Build 6.2.0.28 All CLI Connectivity Kits: All searches for connectstring keywords (like SERVER, DSN) made case insensitive. MSSQLDRV: Added version check for minimum database client version. New driver configuration file (mssqldrv.int) keyword: MINIMUM_CLIENT_VERSION New attribute: DF_DRIVER_MINIMUM_CLIENT_VERSION The default value for minimum client version is 10 SQL Server Native Client 10.0 (SQL Server 2008 client) The version check will be performed during login. Note the first open in a program may also do a login. MSSQLDRV: Changed mssqldrv.pkg to add Function SqlServerClientVersionName Integer iClientVersion Returns String ODBC_DRV: Changed ODBC_DRV_DriverDef.xml to include new attributes for DataFlex 19.0 / Connectivity Kit 6.2: df_file_restructure df_file_restructure_int_only df_file_allowed_structure_changes df_index_sql_type df_index_number

Build 6.2.0.27 Internal build

Build 6.2.0.26 DB2_DRV and ODBC_DRV: Enumeration of tables with function EnumerateTables would not list all tables when one or more tables with comments longer than 128 characters were found.

Build 6.2.0.25 All CLI Connectivity Kits: Reference to index.0 was not written to the INT file in case of an index-only restructure. (A restructure that only involves creating/dropping of indexes). All CLI Connectivity Kits: If no SERVER_NAME was present in the INT file, would cause an exception.

Build 6.2.0.24 All CLI Connectivity Kits: cli.pkg Removed double ifdef All CLI Connectivity Kits: After a failed login with invalid connection id, a connection handle was not released.

Build 6.2.0.23 Internal build

Build 6.2.0.22 MSSQLDRV: Changed mssqldrv.pkg to add constants for “ODBC Driver 11 for SQL Server” (Client for SQL Server 2014) and “ODBC Driver 13 for SQL Server”. (Client for SQL Server 2016) in mssqldrv.pkg. Added new function EnumerateServersLocal.

Build 6.2.0.21 Internal build

Build 6.2.0.20 MSSQLDRV: Added support for “ODBC Driver 11 for SQL Server” (Client for SQL Server 2014) and “ODBC Driver 13 for SQL Server”. (Client for SQL Server 2016). The MSSQLDRV connectivity Kit will now recognize a range of clients that includes ODBC Driver 13 for SQL Server. All CLI Connectivity Kits: Bug in RedirectIdConnectString caused memory error in logout. All CLI Connectivity Kits: Setting a constrain with accented characters did no oem/ansi translation. MSSQLDRV: Changed default map schema for SQL Server (DEFAULT_MAP_DF_TO_SQL_TYPE_SCHEMA) to MAP_DF_TO_SQL_TYPE_SQL2012. Build 6.2.0.19 All CLI Connectivity Kits: A masked time value of 00:00:00 would be passed as " : : ", causing a “Time contains an invalid value” error. This will now be handled as time value 00:00:00.

Build 6.2.0.19 All CLI Connectivity Kits: Restructure prevention changes. Implemented a new table level attribute DF_FILE_ALLOWED_STRUCTURE_CHANGES

Build 6.2.0.18 All CLI Connectivity Kits: Added new DF_DRIVER_CONFORMANCE level bit All CLI Connectivity Kits: Implemented a new setting ALLOWED_STRUCTURE_CHANGES

Build 6.2.0.17 All CLI Connectivity Kits: If an error occurs during open, the driver will now return error 75 DFERR_CANT_OPEN_DATA_FILE.

Build 6.2.0.16 All CLI Connectivity Kits: Bugfix: Setting the value of a SQL_TIME column, could cause memory overwrite. RedirectIdConnectString and RedirectIdConnectStringKeepLoggedIn now combined to single function with bKeepLoggedIn parameter. New RedirectIdConnectString function.

Build 6.2.0.15 New RedirectIdConnectStringKeepLoggedIn function. Amended version of RedirectIdConnectString function.

Build 6.2.0.14 Added new attribute DF_DATABASE_DEFAULT_DATABASE. New RedirectIdConnectString function. MSSQLDRV: Bugfix conversion to SQL Server - CLI_BCP function. When date columns allow nulls (Default_Nullable_Date setting in mssqldrv.int) and no dummy zero dates are used (Default_Use_Dummy_Zero_Date in mssqldrv.int) the conversion will now save 0 dates as NULL in SQL Server.

Build 6.2.0.13 All CLI Connectivity Kits: Setting the DD value of a text column could cause memory error All CLI Connectivity Kits: Moving data to a df_ascii/sql_varchar column, where the data was larger than the field length, could cause a memory error.

Build 6.2.0.12 Added new embedded SQL function SQLConnectionConnect

Build 6.2.0.11 All CLI Connectivity Kits: Trying to open a table that does not exist in the SQL database, an "Invalid cursor state" error would be raised. Now changed to "Table not in connection" error. All CLI Connectivity Kits: Added new driver level setting LOGIN_ON_OPEN and new driver level attribute DF_DRIVER_LOGIN_ON_OPEN New cli.pkg with DF_LOGON_ON_OPEN attribute added.

Build 6.2.0.10 ODBC_DRV: Oracle columns created as type INTEGER returned an incorrect length. All CLI Connectivity Kits: Changing DF_Length of integer type columns is now an int file only change (df_file_restructure_int_only). All CLI Connectivity Kits: When renumbering an index (DF_INDEX_NUMBER) that is the primary index, the df_file_primary_index must also be renumbered.

Build 6.2.0.9 Support for temporary indexes that are created on the fly at runtime. They will only exist as long as the table is open. Temporary indexes will not be created on the server. New cli.pkg: Added DF_INDEX_TEMPORARY as possible value for DF_INDEX_SQL_TYPE attribute.

Build 6.2.0.8 Fixed a bug where create_index did not adjust last_index_number properly

Build 6.2.0.7 Bugfix: SQLConnect crashed when connecting with a not existing connection ID. Bugfix: Opening table with no index definition in INT (system table !) crashed the driver.

Build 6.2.0.6 If a column appears as a segment in a server_only index, the field_index of the column will no longer be set during open. When adding a new index (Create_Index) and there are server_only indexes present, the new index will get the number of the first server_only index. The server_only index(es) will get their index number incremented, so they remain at the end of the index list. Added new attribute DF_INDEX_NUMBER that allows to renumber indexes. New cli.pkg with DF_INDEX_NUMBER added New MSSQLDRV_DriverDef.xml with DF_INDEX_NUMBER added

Build 6.2.0.5 New attribute DF_FILE_RESTRUCTURE_INT_ONLY added. New cli.pkg with DF_FILE_RESTRUCTURE_INT_ONLY attribute added.

Build 6.2.0.4 New index attribute DF_INDEX_SQL_TYPE added. This attribute replaces DF_INDEX_ON_BACKEND attribute. DF_INDEX_ON_BACKEND remains as a read-only attribute for backward compatibility, but should no longer be used. New MSSQLDRV_DriverDef.xml file - added DF_INDEX_SQL_TYPE attribute. New cli.pkg - added DF_INDEX_SQL_TYPE attribute.

Build 6.2.0.3 All CLI Connectivity Kits: During conversion recnum index would be created as client side index.

Build 6.2.0.2 All CLI Connectivity Kits: The default for DF_INDEX_ON_BACKEND was false when creating new index on new table. This caused all indexes to be created as client side indexes during conversion.

Build 6.2.0.2 (merge from 6.1.0.28) All CLI Connectivity Kits: On a standard table with an identity column (df_file_identity = true), when inserting or deleting a column BEFORE the identity column, the identity would not be adjusted. This caused identity insert error during restructure.

Build 6.2.0.1 Improved support for client side indexes. Attribute DF_INDEX_ON_BACKEND is now a read/write attribute.

For full details and a complete list of changes since build 4.0.0.35, please refer to SQL Connectivity Changes and Fixes.pdf available in the ZIP file in the Documentation folder.

Supported Environments 

• DataFlex 18.x and higher
• Microsoft SQL Server 2017 (including LocalDB) using ODBC Driver 13.1 for SQL Server
• Microsoft SQL Server 2016 (including LocalDB) using ODBC Driver 13 for SQL Server
• Microsoft SQL Server 2014 (including LocalDB) using ODBC Driver 11 for SQL Server
• Microsoft SQL Server 2012 (SP3 including LocalDB) using SQL Native Client 11.0
  DB2 10.1 and higher MDAC 2.8
• Windows 7 and higher

ZIP File Contents 

The ZIP file includes five folders containing the following files:
1. Bin Access.int CKDaemon.exe DB1398.dfr DB2_Drv.cfg db2_drv.dll db2_drv.int DB2_DRV_DriverDef.xml DB2rtx.dll MS1383.dfr MSSQLDrv.cfg mssqldrv.dll mssqldrv.int MSSQLDRV_DriverDef.xml MSSQLrtx.dll MySQL.int OD1476.dfr ODBC_Drv.cfg odbc_drv.dll odbc_drv.int ODBC_Drv_Database.int ODBC_DRV_DriverDef.xml ODBCrtx.dll ora_drv_DriverDef.xml Oracle.int Pervasive.SQL.int PostgreSQL.int Register.exe Register.exe.manifest winsetup.dll
2. Documentation SQL Connectivity Recent Changes and Fixes.pdf Whats New in SQL Connectivity Version 6.pdf
3. Help Connectivity.chm
4. Pkg cli.pkg cTableColumnFetchHelper.pkg db2_drv.pkg dir.txt MSSqldrv.pkg odbc_drv.pkg sql.pkg sqlOld.pkg
5. Usr DFErr003.dat DFErr003.hdr DFErr003.tag

Installing SQL Connectivity Kits

Before installing this version of the Connectivity Kit in your production environment, make sure you: + review the documentation installed both in the Documentation and Help folder (see items 2 and 3 under ZIP File Contents) to learn about the changes that this version will bring to your environment + install it in a test environment first to verify the effects this new version has on your existing applications Once ready, install the new build by following the steps listed below:
1. Exit any DataFlex tools or applications so files that need to be replaced are not in use
2. Backup your current DataFlex environment making sure to include the five folders listed above that will be receiving the new files
3. Download the ZIP to a local folder
4. Extract the contents of the ZIP file to the DataFlex root folder where you would like to update/use the Connectivity Kits version 6.2.0.42. For example, if you would like to install this update to be used in a DataFlex 18.0 Studio environment, choose to extract SQL Connectivity Kits v.6.2.0.42.zip to the root folder of 18.0 (default location: C:\Program Files\DataFlex 18.0) - the files will be extracted to the same destination subfolders as listed in the zip. If asked

This ZIP file updates to the latest Connectivity Kit deployment environments that already have a previous version of the Connectivity Kits installed or it will install drivers where no Connectivity Kit has been previously installed.

Recent Changes and Fixes (since Build 6.1.0.18)

The family of SQL Connectivity Kits (including Microsoft SQL Server, IBM DB2 and ODBC) are published as a set. The changes and fixes listed in this document comprise changes made to that set. Some changes are specific to particular CKs and others are generic to the set.

Build 6.1.0.32

All CLI Connectivity Kits: Setting a constrain with accented characters did no OEM/ANSI translation. This was side effect of an earlier fix in 6.1.0.30. Now that is fixed - the translation is happening and constraints should work as expected.

Build 6.1.0.31

All CLI Connectivity Kits: Bugfix: Setting the value of a SQL_TIME column, could cause memory overwrite. This was side effect of earlier fix in 6.1.0.30 A masked time value of 00:00:00 would be passed as "  :  :  ", causing a “Time contains an invalid value” error. This will now be handled as time value 00:00:00

Build 6.1.0.30

All CLI Connectivity Kits: Setting the DD value of a text column, for example:
 

Set Field_Changed_Value of Customer_DD Field Customer.Comments to sText
Send Request_Save of Customer_DD                   

This code could cause memory error if:        

• sText value was the same as the value already in Customer.comments
• An ansi/oem conversion was done

All CLI Connectivity Kits: Moving data to a df_ascii/sql_varchar column, where the data was larger than the field length, could cause a memory error.

Build 6.1.0.29

ODBC_DRV: Oracle columns created as type INTEGER returned an incorrect length.  

Build 6.1.0.28

All CLI Connectivity Kits: On a standard table with an identity column (df_file_identity = true), when inserting or deleting a column BEFORE the identity column, the identity would not be adjusted. This caused identity insert error during restructure.

Build 6.1.0.27

All CLI Connectivity Kits: When calling a stored procedure (SQLCall) that generated informational messages, the SQLGetMessage function would not return those informational messages.

Build 6.1.0.26

All CLI Connectivity Kits: Fixed memory leak in finding/saving. This leak was caused by a change in build 6.1.0.20.

Build 6.1.0.25

All CLI Connectivity Kits: DF_ASCII columns where the underlying type is SQL_WVARCHAR will be trimmed when saved to the database.  WVARCHAR are wide variable length types like NVarchar on SQL Server. This was already implemented earlier for DF_ASCII/SQL_VARCHAR types.

Build 6.1.0.24

MSSQLDRV: When calling a stored procedure with a varchar(max) parameter, the varchar(max) parameter was not passed.

Build 6.1.0.23

All CLI Connectivity Kits: Saving to datetime2 type columns would sometimes save incorrect values. (PM values would be saved as AM values). This could happen when regional settings were set to use 12-hour clock (AM/PM notation).

Build 6.1.0.22

All CLI Connectivity Kits: When changing DF_FILE_LOGIN from normal connect string to DFCONNID connect string that points to the same database, the restructure process would hang.

All CLI Connectivity Kits: Studio would crash at breakpoint if a table had ASC column with length above 255.

Build 6.1.0.21

All CLI Connectivity Kits: On a standard table, having numeric columns with decimals in the primary index, the rowid after a save could be different from the rowid after a find. This could cause incorrect behavior in grids, for example the grid would be cleared after save of a new record.

Build 6.1.0.20

All CLI Connectivity Kits: Using a SQL filter with a length above 64K caused memory overwrite.

Build 6.1.0.19

ODBC_DRV: Some Oracle data types were not properly recognized and would be mapped as DF_ASCII. The Oracle TIMESTAMP type will now be mapped as a DF_DATETIME type. The Oracle RAW type will now be mapped as a BINARY type.  

For a complete list of changes since build 4.0.0.35, please refer to SQL Connectivity Recent Changes and Fixes.pdf available in the ZIP file in the Documentation folder.

Supported Environments

DataFlex 17.x and higher

 Microsoft SQL Server 2012 and higher
 DB2 10.1 and higher
 MDAC 2.8

 Windows 7 and higher

ZIP File Contents

The ZIP file includes five folders containing the following files:

1. Bin

2. Documentation

SQL Connectivity Recent Changes and Fixes.pdf
 Whats New in SQL Connectivity Version 6.pdf

3. Help

Connectivity.chm

4. Pkg

5. Usr

DFErr003.dat

Installing SQL Connectivity Kits

Before installing this version of the Connectivity Kit in your production environment, make sure you:

• Review the documentation installed both in the Documentation and Help folder (see items 2 and 3 under ZIP File Contents) to learn about the changes that this version will bring to your environment
• install it in a test environment first to verify the effects this new version has on your existing applications

Once ready, install the new build by following the steps listed below:

1. Exit any DataFlex tools or applications so files that need to be replaced are not in use
2. Backup your current DataFlex environment making sure to include the five folders listed above that will be receiving the new files
3. Download the ZIP to a local folder
4. Extract the contents of the ZIP file to the DataFlex root folder where you would like to update/use the Connectivity Kits version 6.1.0.32. For example, if you would like to install this update to be used in a DataFlex 18.0 Studio environment, choose to extract SQL Connectivity Kits v.6.1.0.32.zip to the root folder of 18.0 (default location: C:\Program Files\DataFlex 18.0) - the files will be extracted to the same destination subfolders as listed in the zip. If asked, choose to overwrite and replace files in the destination folders.

Important!

If you are using the Windows built-in ability to deal with compressed files and have installed DataFlex into the default location (i.e. under Program Files), when extracting the contents of the ZIP file you may be prompted to use elevated rights in case you are not logged in as Administrator.
 However, if you are using a third-party tool (like WinZip), you may NOT be prompted to use elevated rights and the extraction may silently just not work. Please, follow the third-party tool manufacturer’s instructions on how to extract files when elevated rights is needed.

Support

Data Access Worldwide offers no specifc support for this installation process.

 Support for Connectivity Kits will be included with your DataFlex license and will follow current support policies outlined on the company’s website at http://www.dataaccess.com/resources/customer-support-1196.

 If you have any questions, email support@DataAccess.com.