Hi Mike,

Actually, I was opening and closing the index with SEEK to try and make a fair comparison with LOCATE. My thought was that in code you can just do a LOCATE, but to do a seek you first have to set the order of the table. Anyway, someone else pointed out that SEEK has an optional ORDER clause, as in SEEK 699 ORDER pID. This is quite a bit faster than using just SEEK. Also, it turns out that SEEK is slowed if TALK is ON, but SEEK ... ORDER is not.

>>>
> FOR lnJ = 1 TO 10000
> SET ORDER TO pID
> SEEK(699)
> SET ORDER TO
> ENDFOR
>>>
>
>Hi Brien.
>
>I wouldn't include the set orders in the above code snippet. You already set it before starting this loop. Further, this makes your test not merely compare SEEK against LOCATE.
>
>Try adding SET COLLATE TO "MACHINE" before doing this. SP4 supposedly defaults to something else (?)
>
>SEEK should be way faster than LOCATE.