Icon View Incident Report

Serious Serious
Reported By: Rob Frye
Reported On: 12/10/2008
For: Version 4.27 Build 1
# 2881 Calling CancelRange Before BeginCachedUpdates Causes SetRange When ApplyCachedUpdates is Called

I believe I've run across a bug with cached updates. If a range is set on a table and cancelled before using cached updates then a range will be activated when cached updates are applied or cancelled.

The problem appears to occur because using CancelRange doesn't clear the kiRangeStart/kiRangeEnd buffers so then the SetCursorRange method (called in RestoreRangeAndFilterData) sets an active range.

   ATable.SetRange(...);
   ATable.CancelRange;
   ATable.BeginCachedUpdates;
   ATable.ApplyCachedUpdates;



Resolution Resolution
Fixed Problem on 12/12/2008 in version 4.27 build 2


Products Affected Products Affected
DBISAM CLX Client-Server
DBISAM CLX Client-Server with Source
DBISAM CLX Standard
DBISAM CLX Standard with Source
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source
DBISAM VCL Trial

Image