Icon View Incident Report

Serious Serious
Reported By: Phillip Percival
Reported On: 6/14/2004
For: Version 4.08 Build 1
# 1768 Database Server Is Not Unlocking Records Properly From Removed Dead Sessions

If you terminate an application half way through an UPDATE query, especially if you force an SQL error (eg. invalid column name etc..) and trap the EDBISAMengineError exception then do a "program reset" of the client - the lock on the table being updated appears to get stuck permanently. Its probably not that critical but could occur in the real world if the network goes down or someone turns of the PC at just the right time...

Resolution Resolution
Fixed Problem on 6/15/2004 in version 4.09 build 1