Elevate Software

Login Login

ProductsBulletSalesBulletSupportBulletDownloadsBulletAbout



Home » Technical Support » DBISAM Technical Support » Incident Reports » Incident Reports Addressed for Version 4.29 » View Incident Report

Icon View Incident Report

Minor Minor
Reported By: Jorgen Nim Hansen
Reported On: 11/27/2009
For: Version 4.29 Build 2
# 3160 Upgrading Encrypted Tables from 3.x to 4.x Can Cause CheckSum Errors in Records
I am using Delphi 7 and DBISAM 4.29 Build 2.

After upgrading from ver. 3 to 4 I get the following error in some tables (UpgradeTable):

"Checksum for the physical resord #2 is invalid and the data is likely corrupted)"

Comments Comments and Workarounds
The problem was caused by the upgrade process not taking into account extra padding used to make sure that record lengths fall on even 8-byte boundaries for the 4.x strong crypto. The workaround is to repair the table after the upgrade.

Resolution Resolution
Fixed Problem on 11/29/2009 in version 4.29 build 3

Products Affected 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 More Support Options

Option Search Incident Reports
Option Support Forums
Option Frequently Asked Questions
Option Technical Bulletins
Option Technical Articles
Option Product Manuals
Option Roadmap


This web page was last updated on
Wednesday, October 22, 2025 at 04:21 PM

Privacy PolicyBulletSite Map

© 2026 Elevate Software, Inc. All Rights Reserved
Questions or comments ? E-mail E-mail us at info@elevatesoft.com

Image