Re: [Firebird-net-provider] Subsequent error 'lock conflict on no wait transaction' using TransactionScope across DBs

You have basically only one option. 2PC. But that's not something ADO.NET handles. -- Mgr. Jiří Činčura Independent IT Specialist -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi

Re: [Firebird-net-provider] Subsequent error 'lock conflict on no wait transaction' using TransactionScope across DBs

Thanks for getting back to me. Can you or anyone please let me know what is the recommended approach in the ADO.NET provider for performing a transaction across, let's say, 2 databases (eg a single command in each)? On 5 November 2016 at 08:37, Jiří Činčura wrote: > I don't