David,

I *DO* read the Help. I am reasonably familiar with the Help.

The issue at hand was that the originator (seems to have) assumed that he had a real cursor on his hands, which for all intents and purposes would be equivalent to a TABLE.
What was (apparently) not evident to him was the fact the he did not *necessarily* get a cursor, but could well have gotten a filtered result. This is *NOT* at all clearly documented - not when it happens nor what it actually means (especially vis-a-vis the status of the output of the Select).

SO, before you go about assuming *my* incompetence on the subject, consider your unquestioning faith in the product and ask yourself if the writer (me in this case) truly doesn't understand OR if, perhaps, your blindness prevents you from seeing clearly.

Regards,

Jim N

>Jim,
>
>If you read the help file, RECCOUNT() has always reported physical records in a TABLE unaffected by SET DELETED and SET FILTER.
>
>_tally has always reported the number of records in a SELECT result set, which FoxPro may determine the fastest way of giving you the result is to internally set a filter.
>
>>George,
>>
>>I would agree that, because it is "by design" it is not a "bug". But it is lousy design, to have any command or function which *can* have an *AMBIGUOUS* result. Such things just shouldn't be delivered.