>The UI needs Customer data. It instantiates the MyCustomerBiz class and calls it's GetCustomer() method. The GetCustomer() method in the MyCustomerBiz class instantiates the MyCustomerDataAccess class and calls it's GetCustomer() method. The GetCustomer() method in the MyCustomerDataAccess class takes care of all the DataAdapters stuff and Fills a CustomerDataSet. It passes the CustomerDataSet back to the MyCustomerBiz class. If there's any additional Biz logic that needs to be done to the dataset, it's done here. Then the MyCustomerBiz class passes the CustomerDataSet back to the UI.
>
>The advantage of having separate MyDataSet project is that you can define the CustomerDataSet separately in it's own class. Then each of the three layers can use the same DataSet class.
>
>~~Bonnie
>

Bonnie,

How do you handle differences in between the normalized relational database and how entities may be mapped within the business object? For example, let's say there is an Invoice BO, where you are going to store the custid in the invoice table, but not the customers address. Does your GetInvoice() return a flattened dataset (for the invoice header), containing the customer address, or does the dataset have separate tables containing all of the relationships that might exist in an Invoice?

Thanks for all the info in this thread :)