http://weblogs.asp.net/aaguiar/archive/2004/09/27/234899.aspxWhen building SO applications you usually need to write code to compensate failing transactions. When you call two services that can't (or shouldn't) be called in the same transactional context, and the second fails you need to 'rollback' the first oneenCommunityServer 2007 SP1 (Build: 20510.895)http://weblogs.asp.net/aaguiar/archive/2004/09/27/234899.aspx#6471482Sat, 02 Aug 2008 16:34:31 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6471482lieu s greenville sclieu s greenville sc<p>Pingback from &nbsp;lieu s greenville sc</p> <img src="http://weblogs.asp.net/aggbug.aspx?PostID=6471482" width="1" height="1">http://weblogs.asp.net/aaguiar/archive/2004/09/27/234899.aspx#409296Fri, 27 May 2005 11:09:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:409296TrackBackTrackBack<img src="http://weblogs.asp.net/aggbug.aspx?PostID=409296" width="1" height="1">http://weblogs.asp.net/aaguiar/archive/2004/09/27/234899.aspx#409293Fri, 27 May 2005 11:06:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:409293TrackBackTrackBack<img src="http://weblogs.asp.net/aggbug.aspx?PostID=409293" width="1" height="1">http://weblogs.asp.net/aaguiar/archive/2004/09/27/234899.aspx#235007Tue, 28 Sep 2004 01:25:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:235007BillBillFortunately, they added a .AcceptChangesDuringUpdate feature in 2.0 that greatly simplifies this situation - it's definitely not the most straightforward thing to deal with now but like you showed, it's doable. <img src="http://weblogs.asp.net/aggbug.aspx?PostID=235007" width="1" height="1">