A funny index discovery I've made:
index on something tag A
index on something else tag A
After the second index, the correct records show in browse. But when I run through the records with Scan, For, While, the wrong number of records is sometimes processed, particularly if there are non-unique keys after the second index. But it works fine with:
index on something tag A
Delete tag A
index on something else tag A
Designed behavior, or ??
The Anonymous Bureaucrat,
and frankly, quite content not to be
a member of either major US political party.