You have to add NOFILTER or READWRITE clause to a query to force VFP to create a "real" cursor instead of filtered one. The filtered cursor cannot be used in subsequent queries because it's created as USE AGIAN + SET FILTER on the source table

>Same problem exists in version 8.0.
>

>1.  select * from aliasname
>2.  select * from dbf('aliasname')
>

>We have a method which is passed a cursor name. It appears in that if the cursor was created using the "Create Cursor" command you would use #1. But, if it was created from a "Select ... Into Cursor " command it needs #2. However, our method does not know how the cursor was created, its name was passed to the method as a parameter.
>
>How does the method know which format below to use to select from the cursor?
>
>Note: #1 above used to work in all cases for us until we did some Microsoft Patches recently. Code that had been working for years is now expecting the "dbf(' ')" function - but only sometimes. It does not seem to be consistent.
>
>The error message you get if the cursor was created from another SELECT ... INTO CURSOR statement is:
> "'cursorname' must be selected with SELECT ... INTO TABLE"