>>It does sound like it might be the editbox making the change then. Try removing it as the control source for the edit box and see if the field state still changes. Otherwise, add a watch for GetFldState("YourField","YourTable") and set a breakpoint on it to see what is actually making the change.
>
>I'll try to check it although I already fixed the problem. The EditBox class had no custom code at all. I have a feeling it's something internal wrong with GetFldState as even after I returned .f. from RecordChanged method the update was still firing (I originally had buffering mode 3 set for the view). Only after I changed Buffering mode to 5 and also made a change in RecordChanged method for this form to compare original record with current record it stopped calling the UPDATE. Also, OLDVAL and CURVAL returned the same values.
>
>Wondering if anyone else can reproduce a problem.
Check with GetFldState(-1) what field caused the problem.
BTW even if OLDVAL() == CURVAL() the flag can be raised, just because you replace the field with the same value.
VFP didn't care about the value of the field, just about editing it :-)
REPLACE Field WITH Field will set GetFldState() to updated ;-)
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.