>Suppose I have a complex index i = a+b+c where a,b and c are all table fields.
>
>I do this so that records are fetched in the desired order as I step along to modify each one after I've found the first one. (assume I may need to modify the records).
>
>At the time I search, I only know 'a' so I don't think a SEEK helps me.
>
>What I've come up with (that seems to work) is ordering the table by i then LOCATE for a=. I've done some tests to verify that LOCATE searches sequentially according to the current tag order.
>
>Is this the best way to accomplish what I want without using a view?
>
>Must optimization be disabled in order to insure that the search works the way I need it to?

SEEK is still the best in conjunction with SET NEAR ON.

Edward Pikman
Independent Consultant