>>INDEX... for disables Rushmore optimization
>
>I don't think so, Bill
>
>Help reads
>

>When Visual FoxPro can determine that a query should not return deleted or undeleted records, and if no unfiltered index is present, it uses INDEX ON <expression> ... FOR DELETED() or INDEX ON <expression> FOR NOT(DELETED()). 
>
>For example, the following queries are now optimized:
>

IIRC the deleted() is a special case trumping the general rules of no rushmore with indeces with for or not.