The good way is to subclass form controls with some code in ParentClass.InteractiveChange event which will reset cmdSave/cmdRevert.Enabed properties.

>I would like to enable the save/revert buttons on my form to indicate changes have been made, and also, test on deactivation (which is not a problem). I guess I am asking to see if there are any gotchas or better yet , any "best practices" to consider. Maybe avoid some pitfalls.
>
>Enabling the buttons when there is a change at the record level would be fine. Is it best to put such code in the events of each control on the form?
>
>>Well, that depends on what your design is. But, I guess generally speaking, you can use it when you're checking for whether there is anything to revert/save. For instance, when page is deactivated.
>>
>>
>>>>Would the function GETNEXTMODIFIED help?
>>>>
>>>>>Hello all, I need suggestions on detecting changes to my data at the form level