>It definitely depends on what you're doing with the data ... for reporting or maybe for displaying in a grid, perhaps having it all in one table is good. But for the most part (for data entry) I try to keep the tables intact, so I'd have a DataSet containing several tables rather than de-normalizing it all into one table.
>

~Bonnie,

Does this mean the UI has knowledge of the database design? For example, if you decide that you need to change the database design, it could have ramifications to the UI.

So this might be one of the advantages of binding to properties of the business objects. Because in the business object itself, you can map database fields to the proper BO fields...and if a change is made in the database design, you theoretically only have to change the object mapping at the BO or DA level.

Is my beginner in .NET analysis of the situation anywhere close? I'm still on the bubble regarding how I'm planning on dealing with this stuff....