>>Using 'Set Near On' and Seek 'something' should position the record pointer to the nearest matching record. Usually works fine Except when the index is in descending order. In this case the record you wind up on is the next record After the closest match. Tested under VFP 5.0, I have not tried with VFP 6.0. If you repeat this test using FPW 2.6 it works correctly (that is if you assume the above behavior is a bug and not a feature).
>>
>>Now coding a workaround :(.
>Michael,
>Pointer should position itself where the record would be if existed. And it's the case in VFP 5 too, either ascending or descending.
>Cetin

Cetin,

Thanks, I figured out what was happening. It was a combination of 'set exact' setting and the use of a compound index expression. The FPW 2.6 had set exact off and the value being seek'ed only contained part of the indexed expression. The VFP version had set exact on thus giving the difference I observed.

Regards,
Mike