Hi Joel,

I don't think foxuser.dbf has anything to do with this. In short, if select is fully Rushmore optimizable foxpro doesn't create cursor but instead opens source table with command similar to USE AGAIN and uses SET FILTER to filter records. You can add NOFILTER or READWRITE clause to the Select to force foxpro to create a cursor as a temporay file.


>I don't know if anyone else has run into this or not, but it drove me crazy for awhile.
>I had a project that was originally created in VFP7. After opening the project in VFP8 I noticed that one of my SELECT SQL statements was returning the record count of the source table instead of the actual number of records returned to the cursor. See example below.
>
>If I have a table with the following field and records,
>
>mytable.dbf
>nfield
>100
>100
>102
>103
>
>Then run the following select statement,
>SELECT mytable.nfield from mytable into cursor ctemp where nvalue = 100
>
>? RECCOUNT() would return 4, the number of records in the original table instead of 2 as expected.
>
>To correct the problem I had to delete the foxuser resource file.
>
>I am not sure if this was because of the version change or if the original foxuser file was corrupted. Hopefully this may help someone else out because it drove me nuts.
>
>- Joel