There are times where you should not use NOFILTER due to performance hits.
For example, if your SQL statement doesn't have a WHERE clause, don't use
NOFILTER, if it does have a WHERE clause, use NOFILTER unless you need to subquery it. IF you have a parameterized query, then you should use NOFILTER.

Did you catch all that? :)



>>I've always used this method for determining this. In fact, my routine for making a SQL-SELECT cursor r/w checks to make sure that the extension is ".TMP" or it returns an error. And you are correct, RECCOUNT() will return the # of records in the real .DBF file, not the cursor, if it's a filtered view. Just try a SELECT from the command window, and then do a DISPLAY STATUS. It's really very dependant on what clauses you put on the SELECT, though.
>
>I understand what you mean, now that I've been able to produce a filtered table. It does indeed have a dbf extension, since it's the table itself :)
>
>Also, as I theorized, MODI STRU shows base table properties...I'm not sure why you need the DBF check, though, is it legacy code? Now you can use NOFILTER instead, can you not?