Without new BindingContext() on comboboxes or listboxes .NET will chose one of them to be the navigator for your bound controls - I do not use a navigator - .NET is choosing one for me automatically. This was the entire problem. MacDonald's book says this is the correct automatic behavior. Using new BindingContext() was the only solution I could find to alter this automatic behavior.

Documentation: When I read, "The Binding property sets the binding" - I do not consider that documenation--you're not supposed to use the term as the definition. You're correct, it's not an excuse. When you rush incomplete products to market to stomp down competitors... not going to go there right now.

Yes, I am glad that I have it working, Microsoft could have helped and provided documentation; I am also not sure if assigning a new BindingContext() will bite me in the you-know-where later on.

Thanks again Bonnie!


>>>>>>>>>>>>>>>>>>>>I've been doing that since Day One of working with .NET ... now, maybe it was originally done for this reason, but to be honest I don't remember. That was way back in early 2002. I was actually going to suggest that you try setting those datasources in the Load event ... but I wasn't quite sure what was going on from your initial descriptions of the problem ... that's why I was trying to determine exactly what you were doing. Although I'm not quite sure what you meant by assigning a new BindingContext() to each listbox/combobox ... I'm just talking about setting the DataSource, which is basically the same thing.

>>>>>>>>>>>>>>>>>>>As far as Microsoft's documentation goes, yeah, it's lacking in some areas but pretty good in others. .NET is so huge, but I suppose that's not an excuse for less documentation.

>>>>>>>>>>>>>>>>>>But hey, you've got it done and working now! Congrats!

~~Bonnie