Icon View Incident Report

Serious Serious
Reported By: Phil Percival
Reported On: 4/5/1999
For: Version 1.13 Build 1
# 401 Using Unoptimized Filters Between Two Different Instances of an Application Causes Refresh Problems

The unfiltered view of the table appears fine and at first the applied filter gives the correct result [the default aux. names are always of the form "~AUX 1:R0#:X0#" so NAME index follows the primary index (?)]. The problem seems to occur, commonly, after I edit the NAME of the auxiliary record in the filtered set - particularly if I set the name such that the alphabetical order (NAME index) changes the records
position closer to the top of the filtered set. It's as if changes in the secondary NAME index data corrupts the primary index ?

Comments Comments and Workarounds
This problem was related to a refresh issue with unoptimized filters that rely on record scans to satisfy the filter. The problem could be worked around by adding a secondary index that would make the filter optimized.

Resolution Resolution
Fixed Problem on 4/12/1999 in version 1.14 build 1