That's pretty much what I do in my framework. I don't worry about the user putting back the original value. It's too much work and too much code. You'd have to save the value of lChanged for every control. Word, Excel, and other applications don't worry about it. Why should you?

>I have a SetMode method on my baseform class that places the form into either
>AddMode or EditMode.
>
>AddMode is called, of course, when the New Record button is clicked. Edit Mode
>gets called when the form is opened for editing.
>
>In either case, just because the form is up and ready for input doesn't mean the
>user actually changed something.
>
>So I was thinking that in the InteracticeChange method of all data entry controls
>I could do:
>
>

>ThisForm.ValueChanged(This)
>

>
>The ValueChanged method on the form could then be used to turn on a lChanged
>property, which would then be checked to see if in fact changes were made.
>
>This all would be used in cases where buffering is not enabled.
>
>Anyone see any issues with this?