John,

Yep, I'm back home. But working through some deadlines right now.

Since Kevin said he was gonna post something, I figured he already had some blurb written up on this topic. And since I've got to sit down and think through the best way to describe my thoughts on this topic, which I haven't gotten around to doing yet, I've been waiting to see what Kevin has to say, so I can add my 2 cents if I needed to (which I probably wouldn't need to do). He told me he was putting something on his blog, but so far he hasn't.

Did you see what I already *did* post about using an .xsd to define your DataSets?

I'm not sure if you're looking for info for DataSets or DataAccess? I guess by using a TableAdapter you're tying the two of these concepts together, so I suppose you need direction for both.

Unfortunately, I don't think I have anything I've already written that describes the whole process ... using a Typed DataSet class from an .xsd, filling it in your DataAccess class, then passing it back through the layers to the UI layer ... but, that's basically the flow of everything.

~~Bonnie



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