Well, now you're talking design patterns and n-tier design. Do you want to create an n-tier application where you design your objects according to data, business, and user services? There are oodles of resources to read about this...Including MS whitepapers, threads here on the UT (since you're a PUTM, search on "tier" or "design" or "business objects."

The way I have done it and the way I'm trying to do it now is changing. So, I vote for designing as much as possible for nTier, even if you don't actually need it yet.

>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?
>