Thanks Jonathan. My research so far is leading me to Entity Framework - Code First. EF 5 now includes data binding and automatic migrations (db Updates) both of which were needed. Code First seems to be the preferred method and best supported. Linq to Entity or Linq to SQL both look good for the queries. I have been reading about Test Driven Design and like the concept. Writing code to fail and then fixing it seems a bit odd at first but I understand why it could work.

Thanks for the well thought out response. Microsoft is pushing the Entity Framework with DbContext for all new development. They actually say that datasets have reached an end. Any thoughts? Anyone? P.S. I'm talking about an Entity Framework example called Northwind.Net

I've been a developer for many years. Lately doing a lot of VB6 to VB.Net conversion work. Mostly database driven desktop WinForm apps using SQL. I want to update my design work to current best practices (I'm old school) but there is so much to choose from I'm really confused. I've broken my questions down into fundamental parts for clarity. 1. The use of N-Tier architecture appears best. In my case 3-tier (GUI>DB IF>DB). Do you agree? Other advice? 2. I currently use datasets with filtered databinding. I see Linq, SQL queries and Entity Framework as newer options. Which might be better? Combination? Other advice? 3. Can you point me to good examples of good architecture and coding methods? I'm currently studying Northwind.Net. Other good examples? I know this is a broad question and answers may be personal choice but any guidance is greatly appreciated.