The browse window is not just like using a grid in a form. It
is behaviors all its own. I do not think you can implemented
table buffering outside of a form. Therefore, I believed
what you are experiencing is what is expected for row
buffering.
From the command window try the following:
SELECT tblName
? CURSORGETPROP([BUFFERING], ALIAS())
=CURSORSETPROP([BUFFERING], 3, ALIAS())
? CURSORGETPROP([BUFFERING], ALIAS())
=CURSORSETPROP([BUFFERING], 5, ALIAS())
? CURSORGETPROP([BUFFERING], ALIAS())
-myron kirby-
============================
>Try it and see!!!!.
>
>
>>Are you sure in the browse window you have table buffering?
>>-myron kirby-
>>=========================
>>>How come it works well with the browse window open ????
>>>
>>>
>>>
>>>>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.