Thank you for the hint. I have now changed my logic and I am now caching the UpdateCommand, so that I can set the associated transaction property whenever needed. This indeed resolved my issue.
Pierre > -----Original Message----- > From: Jiri Cincura [mailto:[email protected]] > Sent: Sunday, June 13, 2010 5:49 PM > To: For users and developers of the Firebird .NET providers > Subject: Re: [Firebird-net-provider] FbDataAdapter, commands and > transactions > > On Sat, Jun 12, 2010 at 13:55, Pierre Arnaud <[email protected]> > wrote: > > No, I do not call SqlCommandBuilder.GetUpdateCommand. All I do is call > > IDataAdapter.Update on the data set. > > In the first example, you created instance. Maybe it's good idea to > use these commands explicitly and set transaction properties. > > -- > Jiri {x2} Cincura (CTO x2develop.com) > http://blog.cincura.net/ | http://www.ID3renamer.com > > -------------------------------------------------------------------------- > ---- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Firebird-net-provider mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Firebird-net-provider mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
