# 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 ?