By creating our own indices, we were able to get it down to 14 seconds. Now to get permission to have our own indices in the cdx...

Do you know if there is an index on a field named lastname that is using something like alltrim(lastname)... etc and is created in the cdx BEFORE a plain simple index on lastname tag lastname is created, when you do a select statement (from dotnet via oledb) will vfp automatically use the first (bad) tag or will it use the one most optimizable?


>>We are actually using vpn in to remote control a desktop at a client site and then running from there. The VFP app resides there but the data is from there to another location across a T1 with the directory drive mapped for vfp. I'm in the process of getting permission from the client to install a small vfp command utility to test and see if I get the results I expect and can see the indices, et al.
>
>That should help isolate the problem. Probably need to optimize the query to get better speed. Accessing a table that size over a T1 is going to be slow if its not. If the query shows it is optimized then you might check the size of the index file.