Hi Barbara,

I want to know if the seek function looks in the index file of the real table (physical) or the buffered table (vitual) because if you try your code below and you have a browse window open it will return you the opposite.


>You are correct, Myron. I tried it with and without a TableUpdate() command, and the SEEK() worked correctly IF I'd called TableUpdate().
>
>Barbara
>
>>Since you have table buffering do you not have
>>to do a TableUpdate for your change to committed
>>and your indexes updated?
>>-myron kirby-
>>==============================
>>>Create a table with a field call key LEN 10 char
>>>Add a index on that field call key
>>>add 5 records with the SYS(2015) function
>>>
>>>Table test example
>>>Field key
>>>_RTE10A1W7
>>>_RTE10A1W9
>>>_RTE10A1X1
>>>
>>>
>>>Defective code
>>>SET DELETED ON
>>>USE TEST.dbf IN 0 SHARED
>>>=cursorsetprop('buffering',5) && RETURN .T.
>>>set order to 1
>>>? seek('_RTE10A1W9') && RETURN .T.
>>>replace key with 'Hello'
>>>delete
>>>? seek('_RTE10A1W9') && Still return .T.
>>>
>>>
>>>This only append with buffering 4 and 5
>>>
>>>This behavior dissapear if you have a browse window open with this table in it.