>>BTW, your code will fail in case of NULL in one of the field.

The code I posted was just a quick example, but yes it will indeed fail as you've said for nulls. I don't presume to know how and where any of this should be incorporated into your framework or whether this is even a worthwhile endeavour for you or your project(s). I was confining myself to the topic of VFP's ability to check whether a particular field/record was truly dirty without relying on GetFldState(). I can think of many cons to this approach (most have already been mentioned), and only one real pro... enhanced visual user feedback (such as edit/apply/save/cancel type controls enabling and disabling based on real changes). In any event, good luck to you.