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

[Jiří Č. <ji...@ci...>]

I don't think the TransactionScope block is a good idea here (well, it
never is). Having it between multiple databases mean spinning MSDTC and
enlisting there. I don't remember from top of my head whether that works
in FirebirdClient or not. And the ChangeDatabase is ADO.NET non-sense
for MS SQL. In Firebird you can't switch databases. You just need to
open another connection (which is what the implementation does). So I
suppose some transaction is still dangling there on 2nd run.

-- 
Mgr. Jiří Činčura
Independent IT Specialist