<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Transactional Update using TableAdapters</title><link>http://blogs.msdn.com/b/vbteam/archive/2004/08/30/223007.aspx</link><description>As promised, I’ve put together a sample that demonstrates how to create a transactional update using the new Whidbey TableAdapters. http://windowsforms.net/samples/ThreeLevelUpdate.zip In this sample I create a Parent, Child and Grandchild relationship</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>  The Visual Basic Team : Transactional Update using TableAdapters at Restaurants</title><link>http://blogs.msdn.com/b/vbteam/archive/2004/08/30/223007.aspx#6914240</link><pubDate>Mon, 31 Dec 2007 09:57:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6914240</guid><dc:creator>  The Visual Basic Team : Transactional Update using TableAdapters at Restaurants</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://restaurants.247blogging.info/?p=513"&gt;http://restaurants.247blogging.info/?p=513&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=6914240" width="1" height="1"&gt;</description></item><item><title>re: Transactional Update using TableAdapters</title><link>http://blogs.msdn.com/b/vbteam/archive/2004/08/30/223007.aspx#223625</link><pubDate>Tue, 31 Aug 2004 23:10:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:223625</guid><dc:creator>Jeff Davis</dc:creator><description>This seems like a reasonable implementation given the design of the TableAdapter components. I think the manageability of the partial class approach would be improved with a good code snippet, as was suggested on the MSDN Feedback Center.&lt;br&gt;&lt;br&gt;I think if I were to implement this pattern in my application I would want to do the following:&lt;br&gt;&lt;br&gt;1) Create an Interface that has the AdapterTransaction property.&lt;br&gt;2) Implement a code snippet to add the stock logic to implement this interface on every table adapter we create.&lt;br&gt;3) Always require developers to explicitly set the AdapterTransaction and Connection properties anytime they do a fill or save operation.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=223625" width="1" height="1"&gt;</description></item></channel></rss>