>Humm... I see. As I mentioned to Cetin, I haven't used the nofilter clause. Does this mean that if I am trying to select a record set, and the number of resulting records has to be accurate (used for a counter, total, etc.), that means I have to include a NOFILTER clause every time, just to be sure, correct?
Yes, you have to include NOFILTER if you want foxpro always create cursor as temporary table.

>
>If the NOFILTER clause is not supported by other DB's, that then means that I would have to have a conditional add of the NOFILTER clause, depending on the back-end, right?

Yes, you're right again but there are more differences between SQL implementation between DB's than just nofilter.

>
>- Brian
>
>
>>If WHERE clause of select statement is optimazable and only fields from the table is requested, foxpro opens FROM table with AGAIN clause and ALIAS . If subset of the fields is requested than SET FIELDS command used to show only those fields. ? DBF() will return original table name in this case. There's NOFILTER clause that forces foxpro to create cursor as temporary table.
>>

--sb--