Deleted records are physically still in there;
No matter what command you use (e.g. Skip, Seek (!), Count, Scan, when Fox encounters a record marked for deletion, it will internally skip to the first record not deleted (as long as the filter (etc.) complies.

Only at a Pack the record will be physically gone.

You can use a filtered index with FOR NOT DELETED() in order to let all index-related commands not (internally) find the records.

Your literal question "will the delete cause all to be faster" ... -> No. Unless you apply the above (or similar).

HTH,
Peter

>Hi guys...
>
>i want to know about delete environment...
>is it effect with set filtering or locate......
>
>Suppose i have a ton's of record like this..
>
>--------------------------
>month year comp.
>--------------------------
> 1 1990 CSA
> 1 1990 MSC
> 1 1995 MSC
> 2 1993 CSA
> 2 1993 MSC
> 2 1993 MSC
> 2 1995 MSC
> 3 1995 CSA
> 3 1995 CSA
>--------------------------
>
>If i have the records like above...
>and i delete the file that didn't not match with the input from user
>suppose the input is Month=2 Year=1993 and Comp.=MSC
>
>Then i delete the rest of the records that don't match with the input
>is is true that deleted cause the locate or seek much faster, i mean
>it skip the deleted records..............
>
>
>thanks...
>regards,
>tut_arie