Steve,

>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.

Good point. It's been a long day. <g> But, no, this doesn't mean that the UI has to have knowledge of the database design. Think of the DataSets as being Biz Objects, which in a sense they are. The only thing the UI has to know is the DataSet and you can arrange the DataSet any way you want to.

~~Bonnie



>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....