---

 Comments

---

The problem was that the backup functionality was not stripping out the .dat file extensions included with the list of tables provided to the backup, and this would cause the table handling code in the backup functionality to use different lock offsets than the normal table functionality in DBISAM. The lock offsets would be different because the table would be considered different from the table without the .dat extension in the dbisam.lck lock file handling. The end result would be a backup that would execute while other sessions would still be writing concurrently to the same table files, thus resulting in a corrupted backup.

---

 Resolution

---

Fixed Problem on 12/8/2020 in version 4.49 build 4

---

 Products Affected

---

DBISAM Additional Software and Utilities
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source
DBISAM VCL Trial