Does make a difference. You can check using SYS(3054) function. If SET DELETED is ON and there is no index tag on DELETED(), queries are only partial optimizable. Test queries against a 500k-1000k records table (network, not locally) and you will see a big difference in execution time. If you have an index on DELETED(), execution time can be inferior even if the query is fully optimizable .



>Hi Dorin,
>
>>Check if the query is Rushmore optimizable. I isn't, Foxpro will read all the table through network to find matching records. Also, SET DELETED ON has impact on query execution time, better SET DELETED OFF and HAVING NOT DELETED() clause in query statement.
>
>This really does not make a difference. The deleted records are read anyways. Besides, it generally is a bad advice to SET DELETE OFF just because of potential problems in various fields. Just SET DELETE ON at the start of each data session and never turn it on again.
>
>Walter,
>
>
>>>Hi there,
>>>
>>>last week we installed our software on the client's side.
>>>Than we found that the network communication is very slow.
>>>
>>>Here is what we do;
>>>
>>>(At our side the time from question -> answer is about 1 - 2 seconds)
>>>
>>>- Let the user enter a clientname or clientnumber
>>>- Execute a query on a database that is on a server (so that every user has the same (up2date) tables)
>>>
>>>At the client's side the time from question -> answer is about 20 seconds!
>>>
>>>We do not use any Database manager like SQL-Server, just VFP tables and indexes.
>>>
>>>What can I do to improve the performance of this communication?
>>>
>>>Cheers,
>>>
>>>Erwin