Try reindexing the table and see if that helps.

If not, try copying all records to a new table for not DELETED() and see if that clears things up.

>LOL Yes, there's still at least one live, production FoxBASE+/Mac application running in the world today.
>
>...and it's been mighty stable and runs daily since 1992, but lately there's been some odd symptoms and errors thrown that seem to revolve around rows that are (or are supposedly) marked for deletion being encountered by code even though SET DELETED is ON. In troubleshooting this problem today I made the following observations.
>
>. Browsing the table with SET DELETED OFF I could see tons of records both marked for deletion, and others not marked for deletion. This is what I would expect for the table I am working with. No problem so far.
>
>. I then SET DELETED ON and browsed again. This time all of the records with the deletion mark were removed from the browse EXCEPT one!!! Odd!
>
>. I selected the odd record and did ? DELETED() and got FALSE!! WOW!!!
>
>. I then tried DELETE NEXT 1 and got "0 records deleted"... could it be because FoxBASE thinks it's already deleted?
>
>. I then did RECALL NEXT 1 and got back "1 record recalled"... OK, so FoxBase did think it was deleted and recalled it, but then why did it not remove it from the browse when SET DELETED was turned ON?
>
>. I then retried DELETE NEXT 1 and that worked as expected.
>
>. I tried the BROWSE again (with SET DELETED ON) and got nothing but "live" (deleted) records.
>
>So, Fox/Browse thought the record was deleted and placed the deletion marker in the browse window, but SET DELETED and ? DELETED() thought the record was NOT deleted.
>
>I have never encountered this in all my work in FoxBASE+/Mac, Foxbase on the PC, FoxPro and VFP.
>
>Would love to hear any thoughts people might have on this... Would love to know the cause so I can feel comfortable that the problem has been solved.
>
>Thanks.