>This is one scenario for that mess:
>
>Working on a single table indexed by field 'Observatii'
>
>1. field value is 'Ploiesti'
>2. change value to 'Bucuresti' => record still appear in 'Ploiesti' set of records ( order set to tag Observatii)
>3. change value to 'X Bucuresti' => record appear in X.. set of record but when change to 'set order to Observatii descending' appear in 'Ploiesti' set of record
>4. change value to 'Bucuresti' => record appear back in 'Ploiesti' set of recs
>5. change value to empty string => record appear at top of records (ok)
>6. change value to 'Bucuresti' => record appear in proper order (ok)
>7. change value to 'Ploiesti' => record are doubled in grid and appear in 'Bucuresti' set of recs and second record can't be selected and have field Observatii empty
>
>TOTAL MESS!! ; only way to solve this is delete tag and reindex but this goes like this again
>
>
>I AM DRIVING ME CRAZY!

What type of buffering are you using. I saw a thread here a couple of days ago which said that if you have a buffering option set (I can't remember which one), index doesn't get updated until you issue TABLEUPDATE() and then requery. May not be the same problem but sounds a bit like it!