>>It's my understanding that a fully optimized query will actually create a filter on the table instead of giving you a separate cursor or dbf(). So, I'm assuming that if you use the NOFILTER clause you will no longer have a fully optimized query, but you will have a cursor that you can then select from. Am I thinking right on this one?
>
>Hi Scott,
>
>AFAIK, Rushmore won't be affected, but you will take a performance hit from having to write the records to the drive.


Makes sense.

Thanks for the clarification.