SQL Connectivity Kits - Data Access Worldwide Version: 6.1.0.32 Release Date: November 3, 2016 File: SQL Connectivity Kits v.6.1.0.32.zip Introduction =============== Connectivity Kits provide DataFlex Studio, Windows and Web Clients and WebApp Server with database drivers for IBM DB2, Microsoft SQL Server, and ODBC. Use of Connectivity Kits is governed by the license agreement included with the Software Product with which the Connectivity Kit 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 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 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 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. Copyright 2016, Data Access Corporation.