Icon View Incident Report

Minor Minor
Reported By: Rob Frye
Reported On: 6/19/2017
For: Version 4.44 Build 2
# 4561 IndexName Changes Not Being Preserved Across Multiple Calls to BeginCachedUpdates Method

I believe I've run across a bug with cached updates. If the active index is changed for a table after calls have been made to cached updates then the newly selected index will not be used within any following cached updates calls.

For example, the following leaves the original 'ABC' index in effect within the later cached update call.

ATable.IndexName := 'ABC';
ATable.BeginCachedUpdates;
ATable.ApplyCachedUpdates;
ATable.IndexName := 'DEF';
ATable.BeginCachedUpdates;

The problem appears to occur because the IndexName is only applied when FCacheDataCursor is created within TDataCursor.GetCachedUpdatesCursorand isn't updated on later calls when FCacheDataCursor already exists.


Resolution Resolution
Fixed Problem on 6/20/2017 in version 4.44 build 3


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

Image