>>>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:
>>

>
>Hi Gregory
>
>The help on "Using Rushmore Query Optimizations to Speed Data Access" topic says that "Rushmore can use any open indexes except for filtered and UNIQUE indexes."
>
>I've searched what you posted, but can't find it. Can you, please, the topic name in which it is mentioned?
>
>Thanks.-

the page is
Indexes Based on Deleted Records

search on FOR DELETED will bring it up.