After thinking more about this. I think I'll just have to do it using the .Net paradigm, which is always a good thing:

Obviously, the BindingContext (I could be wrong) is designed to retrieve controls that are related to a particular datasource. So, if I want my datanavigation bar (next, prev, etc..), a custom component, to know what controls need their data to be "repositioned" (changing the .position property), I guess I need to add a way for the developer to add the list of datasources to my Nav bar component using the property sheet.

Then, I'll use the list to find the components using the datasource on the form, by using the form's BindingContext. Another option is to have my derived components contain a property that links to my datanavbar. This would allow the components to be on different form, too. Hmmm...

-Jerry