>Well not that strange < S >.
>
>What would you expect if you:
>1) replaced the field with something else, then
>2) replaced the field with the original value.
>3) did the GETFLDSTATE()?

In that case a change (two in fact) actually happened. No big deal, just unexpected.

Alex


>
>I think the way it happens is just the safer way, at some small cost sometimes (when it was updated with the same value).
>
>cheers
>
>>This is not a problem, just a surprise: if you replace a field in a buffered table with the same value that it already had GetFldState(-1,'alias') reports a change. Does anybody else find it strange?
>>
>>Alex