Hiya Jim! ----

I would agree. But I think the base point (all architectural problems put aside) is that you would want to change the property and not the Value of the bound control if it's a hard-bound business rule you're matching.

All things being equal, I would have the CheckBox bound to a custom property of itself....containership and all that.

>
>I repspectfully disagree with my colleagues. If the defined behavior of the control is to change the form's property then that is what you should do. To do otherwise, for whatever reason, introduces an interdependency between the controls and the form.
>
>Future revisions of the form may cause you to change or remove the control that is bound to the property. This would cause code in a seemingly unrelated control to then fail. If the second control updates the form property and then refreshes the form, there is no interdependency between the controls and future modifications won't have the same impact.