---

 Comments

---

Much thanks to Rob for diligently helping us track this one down. This issue has been present since the re-architecting of the DBISAM Database Server for 64-bit compilation, but hasn't been reproducible until now. The problem was caused by SELECT..INTO queries that opened databases in a way that tripped up the database handle tracking in the outer server portion of the DBISAM Database Server. The end result would be an invalid database object reference left dangling in the server that the server would try to free, only to encounter an AV or invalid pointer operation error when doing so.

---

 Resolution

---

Fixed Problem on 12/11/2012 in version 4.34 build 5

---

 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