>First, the auto-quote stuff. Look at the "Message view setup" tab at the top right of this message "pane". Hover your mouse over that and you should see an option to "Enable auto quote".
>
>Now, the second thing is the TableAdapters. Unfortunately what the TableAdapter paradigm does, is to tie your DataSets/DataTables directly to your backend data. This is not good, IMHO. DataSets are meant to be a disconnected representation of your data. In my opinion, a DataSet should know nothing about where it's data came from. That is the job of the DataAccess layer of your application to figure out: the DataAccess layer makes the connection to the database, fills the DataSet, and then passes the DataSet back to the front-end UI layer (either directly via a Biz object or through a Web Service).
>
>In this way, it's easy to swap out your DataAccess layer to connect to another database server (say, switching from SQL Server to Oracle), without it ever affecting your DataSets. And by having your connection strings in a config file, it's also very easy to switch your connections from one database to a different one on the same server (say, switching from a test database to the real production database). You DO NOT want this stuff hard-coded in the application. Sorry, but that's just not the way it should ever be done.
>
>~~Bonnie

Hi Bonnie,

I too am extremely interested in this topic and am also currently using table adapters.

In your first post you mentioned:

>If no one else has chimed in with some concrete examples
>(or links to examples), I can add more to this topic later
>when I'm back home.

Was wondering if you were back home yet :)

I would love some good examples of how to implement this.

Or maybe Kevin has some good links for us?