Apparently, using the [Transactional] attribute to let the .Net handle transactions for us is not working with the 'Microsoft.Jet.OLEDB.4.0' provider, the exact message I get is:
The ITransactionLocal interface is not supported by the 'Microsoft.Jet.OLEDB.4.0' provider. Local transactions are unavailable with the current provider.
I was able to work around this problem by using similar transaction techniques like the ones use on the CSLA 1.X version.
Anyone knows of some quick fix so that the [Transactional] attribute works with the 'Microsoft.Jet.OLEDB.4.0' provider?
Thanks.
rx
The transactioscope attribute is only available if you use it against SQL Server 2005.
Rocky has a link to a trick where you can get it to work with SQL Server 2000 as well on: http://www.lhotka.net/Article.aspx?area=4&id=39c79955-ddc9-42c7-a657-d5c2ed49975e
I doubt that you can get it to work with the Jet OLEDB provider, though.
However, you will be able to use manual transactions.
/Henrik
Henrik:
Oh well, I was hoping to be able to use this new technology when working against Access databases. Manual transactions will have to do for now, I guess the only benefit for the use of the [Transactional] attribute was simplicity of code (I hope) so everything should be fine.
I appreciate your help, thanks.
Henrik:
Oh well, I was hoping to be able to use this new technology when working against Access databases. Manual transactions will have to do for now, I guess the only benefit for the use of the [Transactional] attribute was simplicity of code (I hope) so everything should be fine.
I appreciate your help, thanks.
Copyright (c) Marimer LLC