Seems unnecessary, but maybe a SELECT before the INDEX ON would make a difference?


>>The Help for INDEXSEEK() *does* say that an ORDER has to be set.
>>
>I had overlooked that; thanks, Jim.
>
>
>But (big BUT <g>),
>
>If I alter the first few lines of my sample code to:
>
>

>CREATE DATABASE temp
>CREATE TABLE anytable (pkey I PRIMARY KEY, cChar C(6))
>INDEX ON cChar TAG cChar
>SET ORDER TO pkey
>SET MULTILOCKS ON
>CURSORSETPROP('Buffering',5)
>

>
>The results are exactly the same! Also the same if the SET ORDER line is to tag "cChar."
>
>So what goes on here?