>Hi John,
>
>>I always though I was able to create a SQL cursor (read-only) based on previously created SQL cursor (read-only) but I guess not. I get an error something like "Must SELECT...INTO TABLE" on the second attempt. Thus, I have to do USE DBF("cursor") AGAIN... before the second SQL-SELECT statement. Any reason why?
>
>This will only work when the SELECT statement creates a physical table. Try adding the NOFILTER clause to the SELECT statement that creates the first cursor.
>
>Christof

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?