Hello liming,
Welcome to the MSDN newsgroup.
From your description, I understand you're wondering the proper means to
perform transaction control when using multiple ADO.NET
tableadapter/typeddataset components in .NET application, correct?
As for ADO.NET, it used to provide connection specific transaction support,
that means the transaction's scope is limited to a single connection. Such
single connection specific transaction is started by calling the
"Connection.BeginTransaction" method and associating other command objects
with the returned transaction instance. According to your scenario, you
have multiple TableAdapters (each of them will have a connection object
associated with it), then I think you can consider use the new transaction
control feature provided in the .NET framework 2.0, it is under the
"System.Transaction" namespace.
You can just create a "TransactionScope" class instance and wrap other
connections/commands's creation code within this "TransactionScope"
instance's lifecycle, this will help implicitly establish a transaction
context. Here are some msdn articles mentioned this:
#Implementing an Implicit Transaction using Transaction Scope
http://msdn2.microsoft.com/en-us/ms172152.aspx
#System.Transactions Namespace
http://msdn2.microsoft.com/en-us/sys...nsactions.aspx
Hope this helps.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)