>>>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?
>>
>>Hi John,
>>
>>It may be that the problem has to do with the way VFP creates the cursor. I've never had this problem with a cursor that had to have a physical presence on the disk. I do this all the time with queries that SUM() values and group them together, with this problem. However, it does occur when the query produces a filtered result without having the information forced to the disk.
>>
>>You might try adding the NOFILTER clause to see if this overcomes the problem.
>>
>>hth,
>
>Thanks George. Actually, I just tried directly accessing the original cursor w/o going through DBF() and it now works. Nothing has changed but it now wants to work. Anyway, I'll add the NOFILTER claus just to be sure.

Hi John,

I think that's prudent. I've run into the problem sporadically, it actually seems contingent on the size of the table and the result set coming back. I don't know if this is the actual case, but by adding NOFILTER, you can be sure that it won't come into play.