Jet 4.0 Driver

[Johnny]

Hi all:

I am writing a little demo that imports data from Excel into CRM and am
trying to use the Microsoft.Jet.OLE DB4.0 provider, but I am getting an
error message:

Error: System.InvalidOperationException: The 'Microsoft.Jet.OLE DB.4.0'
provider is not registered on the local machine.

I got this error on both a Vista machine and a WS 2003 SP 2 x64 machine.

I have searched all over the Microsoft web site but have been unable to find
a download for this driver. I have found sites that have service packs for
Jet, but do I not first have to install the original driver itself before
trying to apply a service pack?

Does anyone know where I can find the driver?

Thanks.

 

[Mark Rae]

Error: System.InvalidOperationException: The 'Microsoft.Jet.OLE DB.4.0'
provider is not registered on the local machine.

I got this error on both a Vista machine and a WS 2003 SP 2 x64 machine.

Presumably the Vista machine is also 64-bit Vista...?

Does anyone know where I can find the driver?

There aren't any 64-bit OleDb drivers for anything other than SQL Server.

You will need to force your app to compile to 32-bit (x86) code -
thereafter, everything should work as you expect...

Also, be aware that Jet has been deprecated for quite a while - there are no
plans to port it to 64-bit:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1764293&SiteID=1

 

[Chris Nahr]

Also, be aware that Jet has been deprecated for quite a while - there are no
plans to port it to 64-bit:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1764293&SiteID=1

That's Microsoft doublespeak for "we can't figure out how to
coordinate our teams". The supposedly "deprecated" Jet engine is
still the default database engine for Access 2007! If they want
people to migrate to SQL someone should tell the Office team...

 

[Mark Rae]

The supposedly "deprecated" Jet engine

There's nothing supposed about it:
http://msdn2.microsoft.com/en-us/library/ms810810.aspx

Specifically: "Jet: Starting with version 2.6, MDAC no longer contains Jet
components. In other words, MDAC 2.6, 2.7, 2.8, and all future MDAC releases
do not contain Microsoft Jet, Microsoft Jet OLE DB Provider, or the ODBC
Desktop Database Drivers."

is still the default database engine for Access 2007!

No it isn't. Open up Access 2007 and create a new database - by default it
will be in the new (*.accdb) format.

http://office.microsoft.com/en-us/access/HA100678311033.aspx

 

[Chris Nahr]

No it isn't. Open up Access 2007 and create a new database - by default it
will be in the new (*.accdb) format.

http://office.microsoft.com/en-us/access/HA100678311033.aspx

Which is still based on Jet, and likewise unavailable to 64-bit
applications. From the same page:

"In Office Access 2007, the Microsoft Jet database engine has been
customized for 2007 Microsoft Office system programs. This
Office-specific version of Jet, called the Access Database Engine,
enables integration with Microsoft Windows SharePoint Services 3.0 and
Microsoft Office Outlook 2007 and creation of multivalued lookup
fields and makes other improvements."

The new database engine for developers is supposed to be SQL Server
which _is_ available in 64-bit versions. Why doesn't the Office team
migrate to this format?

 

[Mark Rae]

Which is still based on Jet

It may be *based* on Jet, but it *isn't* Jet - Jet's gone...

 

[Joel Lucsy]

It may be *based* on Jet, but it *isn't* Jet - Jet's gone...

For those interested,
http://blogs.msdn.com/access/archive/2005/10/13/480870.aspx