>>Patrick,
>>
>>According to another FoxPro programmer in the office, to fully optimize the query, the index should be:
>>
>> INDEX ON DELETED() FOR DELETED() TAG whatever
>>
>>Without the FOR clause, every record's delete status is in the deleted index, a series of .T. and .F. With the FOR clause, only the deleted records are in the index.
>>
>>Haven't tried this myself, but he says they tested this extensively at a previous work site.
>>
>>HTH
>Dallen,
>
>As soon as you put a FOR clause on the index rushmore will NOT use that index anymore. So not only is the FOR clause not nercessary, but if you are hoping that Rushmore will use the index it must not be there.


That's what I thought; none of my indexes have for clauses. I was only relaying info from a contract programmer my firm hired because he is marketted as a foxpro expert by his consulting firm. Of coursse, we hired him to work on Access and VB apps :-)