>>when dealing with an index containing a filter, it is not considered for Rushmore optimization.
>Which is contrary to what MS docs. explains. And would you believe that filtered index is much faster than using views? The condition inside the index is rushmore enabled when it is fired but any statement after it is no longer rushmore enabled that's what I've observed so far.

Jess,

Here's a quote from the VFP help file on Rushmore;

Indexing Effectively for Rushmore
Rushmore cannot take advantage of all indexes. If you use a FOR clause in the INDEX command, Rushmore cannot use the index for optimization. For example, because it contains a FOR clause, the following statement cannot be optimized:

INDEX ON ORDNUM FOR DISCOUNT > 10 TAG ORDDISC

Similarly, Rushmore cannot use an index created with a NOT condition. For example, the following expression can be optimized:

INDEX ON DELETED() TAG DEL

But this one cannot:

INDEX ON NOT DELETED() TAG NOTDEL

So isn't this clear that indexes with a FOR clause will NOT be used by Rushmore to optimize commands?