Sergey and others...

Part1
In a *.prg i have with the same requery and the same Index and the same tables
6 Seconds for a requery.
*!* Rushmore optimization level for table datesfiltred: none
*!* Using index tag Delrec to rushmore optimize table etats
*!* Rushmore optimization level for table etats: full
*!* Rushmore optimization level for table resident: none
*!* Joining table etats and table datesfiltred using temp index
*!* Joining table resident and intermediate result using temp index

Display status to file give http://www.Amline.be/Test.txt

Part2
In my application with same table and same code and same index I have 0.6 seconds !
Environment <>

*!* Rushmore optimization level for intermediate result: none
*!* Using index tag Delrec to rushmore optimize table etats
*!* Rushmore optimization level for table etats: full
*!* Rushmore optimization level for table resident: none
*!* Joining intermediate result and table etats using temp index
*!* Joining table resident and intermediate result using temp index

Display status to file give http://www.Amline.be/Test1.txt

4 set are different.

I think that the buffer are also different.

What can do it ?

bernhart


>>Try Cetin suggestion.
>>
>>It is usefull ( generally ) only for tables with more 50% record deleted.
>
>That's not true. Also, with 50% or more deleted records even SEEK will take forever.
>
>>It slow down the insert and delete process.
>
>As any other index. There's nothing special aboud index on DELETED() in that regard.
>
>>If is usefull, you need to implement a PACK process.