Microsoft.Jet.OLEDB.4.0 Linked Server Transactions

Hi All,

I am writing an interface between SQL Server and Access. I have chosen to use a linked server using the Microsoft.Jet.OLEDB.4.0 provider. One of the requirements is to have multiple SQL statements in one transaction, which is where I am encountering the problem. (see below)

BEGIN TRAN

INSERT INTO ACCES...Table

Msg 7390, Level 16, State 2, Line 2

The requested operation could not be performed because OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "HES" does not support the required transaction interface.

I am having a really really hard time finding documentation on the Microsoft.Jet.OLEDB.4.0 provider, specifically I want to know for sure if it supports the ITransactionJoin interface.

The main question is - does MS Access linked servers support transactions?

Thank you for your help,

I have exausted all resources available to me in finding out the answer.

Thanks,
Eric

Hi,

as far as I can remember Access does not support DT.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks Jens,

This really is bad news for me. The previous interface was just dropping a file on the network and then access had a utility to import and update, however this methodology was horrible. If any step errored then it was a nightmare to clean up the mess and restart, and the data is so out of sync it is ridiculous. I am trying to find a more ACID way.

Maybe I can use the linked server to prepare some temp tables, then write a utility in C#.net to do the update. I bet the connection in .net can support non-distributed transactions.

Microsoft, I love you and hate you.

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

Hi folks,
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,

: Msg 7403, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.

Sunny

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft|||

Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?

|||

David Sceppa - Microsoft wrote:

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft

Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')

select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''

from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')

version info from live:

7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

Hi folks,
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,

: Msg 7403, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.

Sunny

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft|||

Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?

|||

David Sceppa - Microsoft wrote:

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft

Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')

select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''

from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')

version info from live:

7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

Hi folks,
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,

: Msg 7403, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.

Sunny

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft|||

Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?

|||

David Sceppa - Microsoft wrote:

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft

Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')

select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''

from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')

version info from live:

7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00