Icon View Incident Report

Serious Serious
Reported By: Jason Wilson
Reported On: 6/28/2013
For: Version 4.36 Build 1
# 3875 CASTing Strings as Memo Types Can Cause Extra Null Terminator at End of String

I think we’ve stumbled upon a bug that appears to have been introduced into the DBISAM components as of 4.34 build 7. Testing with versions prior to this (up to 4.33) don’t exhibit the problem.

Essentially, when appending text to a memo field via SQL, we’re seeing a null byte (#0) getting appended to the field data too. Interestingly, subsequent appends via SQL keep shifting these accumulating null bytes to the end of the field data. However if data is appended via code using a dataset instance, the new data is appended *after* the null bytes.


Resolution Resolution
Fixed Problem on 7/16/2013 in version 4.36 build 2


Products Affected Products Affected
DBISAM Additional Software and Utilities
DBISAM CLX Client-Server
DBISAM CLX Client-Server with Source
DBISAM CLX Standard
DBISAM CLX Standard with Source
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard
DBISAM ODBC Standard with Source
DBISAM ODBC Trial
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source
DBISAM VCL Trial

Image