>Andy,
>
>What I'd suggest is a simple SaveChanges() method that determines whether or not the value has changed. IOW, call RecordHasChanged() from within that method.
>
I usually code like you suggest. But I see Walter's code as another way to do it.

>You must make sure that the testing hierachy won't inadvertantly miss a valid selection because of the order of the CASE statement.

I have been "bitten" by this many times. That's a good point.