Yes.

But new in VFP 7, the oldval() and curval() for corrupted fields are different.
This makes not possible to save a record if it contains a currupted field
and remote updating is used.
Is it possible to get correct values in llOtherUser and llThisUser ?

set multilocks on
create table test ( test n(1) )
insert into test values (10)
use in test
use test
cursorsetprop( 'buffering', 5 )
lcField      = field(1)
llOtherUser  = oldval(lcField)   <> curval(lcField)
llThisUser   = evaluate(lcField) <> oldval(lcField)
* Why llOtherUser and llThisUser are both .T. ?
assert !llOtherUSer
assert !llThisUSer

>The same behaviour you can find in at least in FoxPro2.5 for DOS and in VFP6.
>
>>I encountered the following two anomalies trying to use VFP 7.
>>Can you confirm, are they VFP bugs or not.
>>
>>Bug 1
>>VFP Error does not occur if insert command causes overflow
>>

>>create table test ( test n(1) )
>>insert into test values (10)
>>

>>
>>
>>Bug 2
>>
>>In REPLACE, VFP Error occurs, but data is corrupted
>>
>>

>>create table test ( test n(1) )
>>APPEND BLANK
>>on error note
>>* this line produces error but data is corrupted.
>>REPLACE test WITH 10
>>on error
>>SET ASSERTS ON
>>* this assertion fails.
>>ASSERT test=0
>>