Thanks for your reply Brian. I am close to resolving my problem this way. Since each combobox needs a different list of data, I chose to use entitylists (V2.4) to bind the DataSource to. Using this approach, each lookup control instantiates its own lookup BO. Creating views on the underlying data table is no longer needed since the data isn't shared by controls. Registration of the object with the form isn't necessary.

The remaining obstacle I have is where to bind the control to the datasource. The control has a browsable "Lookupkey" property the user can set in design mode. However, the property doesn't appear to get it's value from the form until after the control's constructor completes. I placed the logic to bind the control in the bindingcontextchanged() method which appears to fire after the "lookupkey" gets its value, but I don't believe it is the best place to put it. The BindingContextChanged method is called after I bind the control so it fires unnecessarily. Do you know of an event I should use?