Icon View Incident Report

Serious Serious
Reported By: Matt Lewis
Reported On: 9/9/2016
For: Version 4.43 Build 1
# 4434 64-bit ODBC Driver Not Working Properly as SQL Server 2016 Linked Server

I emailed a few months ago where I reported an issue with the DBISAM ODBC driver being used in a linked server setting on SQL Server 2016. The problem is that rows of data are returned but they have no values.

Anyway, I am trying to set up another link server connection for a different customer – and the problem is still evident even though I’m using a different machine. I initially thought the collation settings might be a problem and I’ve tried many different settings to no avail.


Comments Comments
The bug was that SQL Server 2016 was using row-wise binding with a bind offset, and the DBISAM ODBC Driver was not properly handling the bind offset as a 64-bit integer, causing an internal AV in the driver when trying to fetch rows.


Resolution Resolution
Fixed Problem on 9/26/2016 in version 4.43 build 2


Products Affected Products Affected
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard
DBISAM ODBC Standard with Source
DBISAM ODBC Trial

Image