Just a thought about mapping my business tier to the database object model. This is easy enough when you have three tables and one or two keys... but in my work I often have applications that consist of about 30 tables and each table have three or four keys. Now things become really painful. Of course still there are objects I can separate, but what is there to do when the relationships become so painfully complex?

For example, let's say I want to show a datagrid of some data based on input parameters and about 6 db tables... How should this be coded in the business tier?

It is much more complex than the example I see everywhere where you want to list a "customer" table... it's easy you have a serializable customercollection that you can bind to your grid

dim oCustCol as new CustomerCollection

mydatagrid = oCust.Load
OR with parameters.. an overloaded Load method
mydatagrid = oCust.Load(txtName.text, txtZip.text)

And there you have it. But what about the "real world" complex situations? I don't see any articles about them... even with the northwind db an advanced business tier could be designed...


kind regards
Henrik