---

 Comments

---

In 4.20, we added a check for this type of problem and had it trigger an #8965 engine error if it found the condition. The problem was caused by the change detection kicking in due to a .dat or .blb modification only. This would cause the .dat record buffers and .blb block buffers to be freed, but DBISAM was not freeing the .idx page buffers. However, the higher level table cursor performing the operation that caused the change detection expected the .idx page buffers to be freed and would
re-request the same .idx page buffer without first putting the one it had back. This would cause the "double-pin" situation that the above-mentioned check was intended to catch. The usage count for the index page buffer would go to 2 and never get below 1 again, preventing DBISAM from flushing it to disk as needed when it was dirty due to modifications during an append, update, or delete.

Many thanks to Roy Lambert for sending us a project that replicated the problem. We tried to replicate this issue for many months before we were able to do so with his help.

---

 Resolution

---

Fixed Problem on 6/16/2005 in version 4.21 build 4

---

 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 VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source