DISTRIBUTED TRANSACTION with OLE DB Jet

Hi,
I set up an Access 2003 MDB file as a linked Server on SQL Server 2000.
I like to use it to sync entries between SQL Server and the MDB Database.
For this purpose I like to use a DISTRIBUTED TRANSACTION.
But this is the result I get when I use COMMIT TRANSACTION at the end.
<eb1>The current transaction could not be exported to the remote provider.
It has been rolled back.
State: 42000, Native: 8524, Source: Microsoft OLE DB Provider for SQL
Server</eb1>
Thanks for any help
Regards
Patrick
Please reply to group, rather than mail ad patrickwolf - netJET does not support distributed transactions, therefore this will always
fail.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Patrick Wolf" <pwolf@.SeeSig.Invalid> wrote in message
news:OIgjIYOZFHA.3852@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I set up an Access 2003 MDB file as a linked Server on SQL Server 2000.
> I like to use it to sync entries between SQL Server and the MDB Database.
> For this purpose I like to use a DISTRIBUTED TRANSACTION.
> But this is the result I get when I use COMMIT TRANSACTION at the end.
> <eb1>The current transaction could not be exported to the remote provider.
> It has been rolled back.
> State: 42000, Native: 8524, Source: Microsoft OLE DB Provider for SQL
> Server</eb1>
> Thanks for any help
> Regards
> Patrick
> --
> Please reply to group, rather than mail ad patrickwolf - net
>|||> JET does not support distributed transactions, therefore this will always
> fail.
Thank you Gert. Its a pity but its good to know :)