Thanks a lot for your suggestion Fabio, which surely works in this case. My real problem is though (if you can understand me), I don't really want a solution that requies "coding change" (like the one you provided here or the "RELEASE m.c2" statement before the GATHER). This is because the "for !deleted()" index filter is something I newly introduced to some of our tables, without it (i.e. if the index had been built with just "INDEX ON c1 TAG c1 CANDIDATE") all our existing code works just fine. So my question is, when something like this is introduced at the TABLE level, can I somehow avoid it breaking all the existing code, so that all our developers don't have to check everywhere in the application and make a CODE change to fit the TABLE change?

Cheers, Abe