Icon View Incident Report

Serious Serious
Reported By: Ralf Bieber
Reported On: 3/3/2004
For: Version 4.04 Build 1
# 1592 Using Optimistic Locking Protocol Can Cause Unlock Errors When Changing Records with Active Filter

Version 4.04, C/S, Lockprotocol=lpOptimistic. When a filtered or ranged field is changing, then occur a unlock error (10242). If the changing is not canceled and the application is canceled, then is this record locked. You can't edit this record (error 10258), so long the breaking user connection is not remove. The file "dbisam.lck" lock the system. You can test it with dbsys.

DBISAMTable1.Filter :='not KZ';

procedure test;
     DBISAMTable1.FieldByName('KZ').AsBoolean :=
          not DBISAMTable1.FieldByName('KZ').AsBoolean;

Comments Comments and Workarounds
The workaround is to use pessmistic locking instead.

Resolution Resolution
Fixed Problem on 3/19/2003 in version 4.05 build 1