Hi Stephen,

What is happening here is that the ValueMember of the ComboBox is being set after the DataSource. This causes the SelectedIndexChanged event to fire during initialization. If Kevin reverses the order of the population of the properties, this extra firing will not occur. I'm sure Kevin will look at this after he returns. You can detach the event in the Form_Load to prevent the unwanted event from firing and then reattach it after the binding of the control for now or you can leave you code as you have it.

>Correction, the SelectedValue initially contains a DataRowView instead of DataRow. Before the form actually shown on the screen, the SelectedIndexChanged event fired 3 times, the first 2 times SelectedValue contains DataRowView but the last time it contains integer.