>Just to play devil's advocate- isn't refreshing the entire form overkill for this?
>
>If so, then the logical conclusion would be to refresh the single control that is bound to the form. To refresh that control, you have to know it's name, and that is the same type of object dependency Jim was advising to avoid.

Erik,

Sorry for the delay, I lost a hard drive while on the road and couldn't get here. The dependencies are not quite the same. If youupdate the control's value proeprty when the goal is to update the form's property, then there is a dual dependency in the code, one the control IS bound to the form's property and the control's name is what you think it is.

It is less problemsome for a container to know about the thing contained than it is for sibling objects to have awareness of each other, so it would appear to me that the best approach is to have the form's property use an assign method to refresh the control, then the other code simply assings a vlaue to the form's property and the rest is handled.