Why no good resources on junction table scenarios?

[Earl]

Over the years I've read a lot of good books, articles, even posts on
ADO.Net. But when it comes to anything more complex than single or multiple
single table updating scenarios, there seems to be a dearth of good
information. Surely there is a good MSDN article on better techniques for
handling this scenario, as ADO.Net does not seem like a very good solution.
The best I've been able to do is using a stored procedure transaction but it
really seems to hack the whole idea of ADO.Net.

 

[William \(Bill\) Vaughn]

ADO.NET and Visual Studio are designed to generate code for the simple
table-update case. Once you graduate to more sophisticated relational
designs, you'll probably migrate to stored procedures--most developers have.
These blocks of server-side logic handle the complexities of multi-table
updates. Yes, I address these approaches in my books.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...

 

[Earl]

I've always used stored procedures in my ADO.Net apps, the problem is more
with how to submit transactions back from multiple related data tables that
include a junction table. In your book from 2002 (ADO.Net and ADO Examples
and Best Practices), you have a passage that reads, "Beacuse I don't really
endorse client-managed transactions, if you choose this path, I'm going to
leave you to your own devices." Is this the scenario to which you are
referring?