Jim,

TABLE != CURSOR.

The help for SELECT-SQL does not list reccount() in it's see also, it lists _tally because that's the appropriate value to find the number of rows in the cursor.

You complained about the amiquity not the orignal poster. I was trying to clear up your ambiguity.

You quite incorrectly assume my faith in the product and are quite unaware of the numerous bugs that I've report to MS starting with FPW2.5 which where I began using FoxPro. Where there's a bug, I report it and work around it. Where I don't understand how FoxPro works I seek to understand it. Just because it doesn't always work the way I first assume hardly qualifies it as a bug, or design flaw or even those things that don't quite work as we want them to because the MS design team made decisions and design assumptions that make the language work in particular ways. Any language is like that, XBase is full of these kinds of things to go way back beyond Fox.

Visual FoxPro is a great tool, currently it is my primary tool of choice but it's not the only tool I use, heck I even use some non-Microsoft tools. *s* Please don't equate my messages clarifying and explaining things or my MVP status as blindness.

I just get tired of seeing your complaints about the product, rather than offering solutions/workarounds to the people asking the questions.

If you think the help file is incomplete or unclear send an email to foxwish@microsoft.com with suggestions on how it can be improved.

>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.