Hi Charlie,

Apologizing for my persistence here, but you say "and it apparently has for years".
My guess is that this is based on testing you just did using FP 2.6. I really would like to know if this FP 2.6 test was done on a system *never* touched by any other version of VFP.

I have outlined WHY I feel this is crucial, but add to it that, for literally years now the "common wisdom" has alweays been to make an index on DELETED(). In fact the Hacker's Guide tells people to do exactly this 'never mind the actual occurrences of deleted records in a table'.

So I think it is *NOT* reasonable to state that things have apparently been this way for years. To me it definitely has the feel of something "broken", and recently too.

I am glad that you will submit it to MS.

Jim N

>Lance,
>I think this is something MS could/should fix. I will try to send this scenario to them.
>
>If you SEEK(Expr, Alias, TagName) with a SET ORDER TO AnyTag, it's fast--even across the WAN. Again, my testing just assumes if there is much network traffic and the table(s) I'm using are accessed through the WAN connection, anything faster than 2 seconds means there was a minimum of packets. If any unusual traffic occurs, we quickly get minutes of elapsed time, not seconds. GO RecNum with SET ORDER TO SomeTag or without, SET DELTED ON/OFF, DelTag in place or not, makes no real difference. All is fast. I just tested GO TOP and GO BOTTOM with all options DELETED ON/OFF ORDERED, and found all of them to be fast. LOCATE with no condition was fast, unless the table has a DelTag and SET DELETED is ON--which makes sense.
>
>The main point is LOCATE when an ORDER is SET reads the index file unnecessarily, and it apparently has for years. I guess the answer for now is--don't do that.
>Charlie
>
>>
>>Another thing to consider is that this was all going on over a fairly heavily used network to begin with and the NT Workstation and even the server weren't running on particularly zippy hardware.
>>
>>I couldn't believe they found it acceptable and didn't call me. If I hand't gone on site I never would have found this problem. They would just start a query and go on break, so they actually were rather fond of my software. :)