Hi Fabio,

1. == is not optimized
2. Set exclusive on is not optimized either.

What drives me crazy is that my setup with my tables (DBF) on a Windows 2000 SP4 server is a very typical scenario AFAIK. And VFP9 must read the LAN index, because it surely uses it for the integer field.

>>Hi all,
>>
>>I have read more or less all threads regarding VFP9 the last year, but now I face a problem which I can not remember having heard about.
>>
>>I try a standard SQL select statement, SELECT * FROM myTable WHERE myField=myValue. MyTable has about 700,000 records and is located on a WIN2K server and is shared by many users, all running VFP8. MyTable has many index tags, also on myField. When I run the query on VFP8, the query is fully optimized and is instant. Running VFP9 on the same table, SYS(3054,11) shows no optimizing and takes 7 seconds. Can anyone tell me what I can do to get my speed back into VFP9?
>>
>>Update:
>>I copied the table to another filename on the same server, and removed all the other index tags, and the result was the same, slow on VFP9, instant on VFP8. MyField is C(17), I have tried all the different collate sequences with the same result. But when I copied the table to C:, the query was instant on both VFP8 and VFP9. Now I am even more confused!
>>
>>Even one more update: Another field in the same table is integer, and has an index tag, and a query in that field is always instant.
>
>Hi Tore
>

>i think that VFP9 purge the myTable's cache, and skip to read a LAN index.
>

>
>1. try with ==
>
>2 test it with SET EXCLUSIVE ON; obtain you the same one ?
>
>Fabio