>>I covered this in my recent presentation on Rushmore to the Toronto Ontario FoxPro Users Group. This was written up in FoxPro Advisor by someone else too. If you have SET DELETED ON, you will only be told you're getting full optimization if you have that tag. However, pulling that tag across the network slows things down. It is the reverse on a local drive. Since I only build stuff for networks, I now ALWAYS test queries by setting deleted off and never have an index on deleted(). That way I am told I'm getting full optimization for the parts that really matter.
>
>Have you also tested with binary index? AFAIK the binary index is a lot faster than an ordinary index.

Yes, binary indexes are faster but the pipelines (LAN/Local drive) are still the bottlenecks. Look at it this way, if it takes 8 bytes for 8 records, that's 64 bits of data transfer. If I use binary it's now 8 bits of data transfer. If I have no tag, it's zero bits of transfer.