View Incident Report

Serious

Reported By: Reijo Pitkanen
Reported On: 10/5/2012
For: Version 4.34 Build 2

# 3664 Import Table Functionality Can Experience an AV

There is now something changed in CSV-import in the DBIsam System Utility.

I do a lot editing DBisam data in Excel (open office calc) so that I first export the table to CSV text file (tab delimited 09H) using DBIsam System Utility and then edit data with Excel and then import it back to DBisam with System Utility.

Now with version 4.34b1 export works normally, but import gives AV or illegal data in the first imported row.

Comments

This was caused by a cleanup in the code as part of the fix for incident #3623. The import code was relying on some improper code in the expression conversion functionality, and once that was fixed it broke the import functionality.

Resolution

Fixed Problem on 10/6/2012 in version 4.34 build 3

Products Affected

DBISAM Additional Software and Utilities
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

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap