David,

>Do you know the answer to my final question? Why does VB put a Save method in the form but nothing else? Where does VB put the Add and Delete methods?

No, I don't know, sorry ... but one of those articles showed how to generate some of that stuff I believe. I don't remember exactly which one or where it was in the article ... I only skimmed them last night before I posted my reply, but I seem to remember something about this in something I read last night.

~~Bonnie



>Bonnie,
>
>Thanks for the reply and the links; the Brian Noyes article does look very interesting and I've printed it for later perusal. One of your other links answered a question I had a couple of months ago, which was why does it take so long to change the connection string when moving a program to a new computer.
>
>I can assure you that I am no fan of table adapters myself; in fact, I gave up on VFP8 because it relied on what I called CursedAdapters and I much preferred the SQL PassThrough that I used in VFP6. I look forward to having the time to do away with adapters in my VB programs altogether, a la Brian Noyes, but a pressing deadline won't allow that right now.
>
>Do you know the answer to my final question? Why does VB put a Save method in the form but nothing else? Where does VB put the Add and Delete methods?
>
>Thanks,
>David.
>
>
>>Sorry, David ... this doesn't really answer your question at all, but I felt compelled to post. <g>
>>
>>This is my pet peeve. What you're doing is putting your DataAccess into your UserInterface. This is not considered one of the "best practices" for application design. You really want to have a totally separate Data Access Layer. Read the info in the following article by Brian Noyes. He makes some good points, and also discusses some TableAdapter ideas (including some stuff that may help to answer your questions):
>>
>>http://www.theserverside.net/tt/articles/showarticle.tss?id=DataSetDesigner
>>
>>I haven't read the whole article, but what I've read is pretty good (although he misses the boat on what to return from a Web Service, IMHO ... but that's a whole 'nother discussion <g>).
>>
>>Here's another article I found about n-tier and/or n-layer applications. This article deals with a Web application, but the basics apply to a Windows application as well.
>>
>>http://www.aspnetpro.com/NewsletterArticle/2007/02/asp200702dw_l/asp200702dw_l.asp
>>
>>I also wanted to rant against TableAdapters ... I just don't like them, but I thought I should back up my opinion with a few articles and blogs:
>>
>>http://adoguy.com/2006/06/08/TableAdapters_-_A_Critique.aspx
>>http://objectsharp.com/cs/blogs/bruce/archive/2007/06/05/connection-strings-and-tableadapters-revisited.aspx
>>
>>There's more rants against TableAdapter out there. And probably just as many that *like* TableAdapters. But I was getting tired of all this Googling. <g>
>>
>>~~Bonnie