I read your article in the FAQ section. It was very helpful in explaining the problem. Thanks for your advice.

>>When I first started programming in VFP (about three years ago), I was told that I needed to have an index for each table on DELETED(). It was supposed to speed things up a bit.
>>
>>Recently, while reading several threads on the UT, I have found that some here say there should not be an index on DELETED() - that it actually slows things down?
>>
>>So, before I go back and take out all those indexes, I though I'd ask the question here to see what everyone thought. Should I have an index on DELETED() for every table or not?
>>
>>Thanks for your help!
>
>Having an index on DELETED() will help you achieve "Full Rushmore Optimization", by definition. But "Full Rushmore Optimization" is not always optimal. Please read my recent entry in FAQ for a detailed explanation.
>
>Access with too many indices (especially an index on DELETED()) will be especially slow if you a) have scores of thousands of records, b) access data over a network.
>
>Hilmar.