Nope. The record pointer WILL be moved to the first record in the index that has the same deleted status as the current record. The only situation when the pointer is not moved is when the current record is the first to match the condition, but this is a special case.

SEEK looks in the index. It doesn't test the current record and if it matches the condition remain on it.

Vlad

>That is the correct answer. Here's why.
>
> SEEK DELETED()
>
>will not move the record pointer at all, because DELETED() returns T/F for the deleted status for the current record. If the current record is deleted, DELETED() returns .T. and we are on a record that meets the condition of the SEEK. If the current record is not deleted then DELETED() returns .F. and we are on a record that meets the condition.
>
>To find the first deleted record you need to SEEK .T. and to find the first not deleted record you need to SEEK .F.