MS Access Linked Tables under SQL 2005 x64?



I am running the 64-bit x64 version April CTP SQL Server 2005 under Windows
2003 Server x64 Edition. I am trying to create a Linked Server to a
Microsoft Access database, it does not show the Microsoft.Jet.OLEDB.4.0 as
one of the available providers.

I can programatically create the linked table by executing the
sp_addlinkedserver and specifying the 'Microsoft.Jet.OLEDB.4.0 provider, but
when I try to run a query against that linked server, I get the following
error message:

Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

I would appear that SQL Server 2005 is only seeing the 64-bit OLE DB
providers. Is there a way to get it to recognize/use the installed 32-bit
providers on the system?
.



Relevant Pages

  • Re: Installing foxpro oledb on SQL 2005 64 bit
    ... Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP ... Is there a 64 bit OLE DB provider for ODBC? ... You mean third-party OLE DB providers designed to ...
    (microsoft.public.data.oledb)
  • Re: Installing foxpro oledb on SQL 2005 64 bit
    ... None of the ole providers on my 64 bit SQL 2005 seem to suggest that they are ... Is there a 64 bit OLE DB provider for ODBC? ... Over time new data features have been added to FoxPro tables. ...
    (microsoft.public.data.oledb)
  • Re: Installing foxpro oledb on SQL 2005 64 bit
    ... Other OLE DB providers? ... You mean third-party OLE DB providers designed to ... Over time new data features have been added to FoxPro tables. ...
    (microsoft.public.data.oledb)
  • Re: Slow ADO.NET Drivers
    ... This is a list of the OLE DB providers--if Informix is there, ... >> ODBC.NET managed providers are about 20% faster but YMMV. ... >>>> Are the Informix drivers using OLE DB or ODBC? ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: SQL Server 2000 64-Bit
    ... OLE DB providers need to be 64bit ... Regards ... > version in order to address more memory for Analysis ...
    (microsoft.public.sqlserver.server)

Loading