In case you didn't see it, there was an in-depth article about this in the May 1999 FoxPro Advisor ("Rushmore: Less is More", by Chris Probst, pp. 34-39) which supports this finding. Well worth reading.


>Rick,
>
>>You asked about maintaining an index on DELETED(). The conventional wisdom is that you want to do this for performance reasons in any case, although there has been some dispute about this too.
>
>We just had a thread here yesterday about a 1.5 million-record table with up to 2 minutes delay with

USE table
>BROWSE

before the first records appeared. It was a case of zero deleted records in the table, but the DELETED() index was still being read. Removing the DELETED() index tag reduced the wait to 3 seconds.
>
>So there are reasons for the dispute about the conventional wisdom. I'd say test it both ways with full-size typical data tables for each different app and installation.