>All that said, if you do away with the dataset and just bind directly to the Business Object you won't have this issue.

My confusion with using a BO is that I cannot yet figure out how to have one control on my form display one set of data from a BO, (i.e. a stored proc result), while having another control on the form that uses the same BO, but displays a different data result set. From my first testing, it seems that when you fire a BO call, all controls that are bound to that BO will update to the same exact data set.

Imagine one combobox displaying active customers (cust_status="A"), and another combobox displaying inactive customers (cust_status="I").

How would you structure this using a BO model? I'm wanting to learn the BO stuff, but I do not yet grasp some of the fundamentals like this.

That's why I thought DataSets might be the answer, but maybe not.

i.e.

dsActiveCustomers=BO.GetActiveCustomers();
dsInactiveCustomers=BO.GetInactiveCustomers();

then bind each ds to it's combobox?

Also, for now, I am not so much wanting to BIND for CRUD purposes, I just want to use the combboxes to get user choices, and the run SQL statements to pull back and display static data based on what they choose.