Partilhar via

How to get a x64 version of Jet?

  • Artigo

We have had a number of people ask about how they can get the Jet ODBC driver/OLE DB Provider as 64 bit.  Windows only ships the 32 bit versions of these.  The answer is that the windows versions won’t be x64 as those items are deprecated.  What does deprecated mean?  Here is the excerpt from the MDAC/WDAC Roadmap on MSDN:

Deprecated MDAC/WDAC Components

These components are still supported in the current release of MDAC/WDAC, but they might be removed in future releases. Microsoft recommends, when you develop new applications, that you avoid using these components. Additionally, when you upgrade or modify existing applications, remove any dependency on these components.

And here is what it lists about the Jet Database Engine:

Microsoft Jet Database Engine 4.0: 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/WDAC releases do not contain Microsoft Jet, the Microsoft Jet OLE DB Provider, the ODBC Desktop Database Drivers, or Jet Data Access Objects (DAO). The Microsoft Jet Database Engine 4.0 components entered a state of functional deprecation and sustained engineering, and have not received feature level enhancements since becoming a part of Microsoft Windows in Windows 2000.

There is no 64-bit version of the Jet Database Engine, the Jet OLEDB Driver, the Jet ODBC Drivers, or Jet DAO available. This is also documented in KB article 957570. On 64-bit versions of Windows, 32-bit Jet runs under the Windows WOW64 subsystem. For more information on WOW64, see https://msdn.microsoft.com/en-us/library/aa384249(VS.85).aspx. Native 64-bit applications cannot communicate with the 32-bit Jet drivers running in WOW64.

Instead of Microsoft Jet, Microsoft recommends using Microsoft SQL Server Express Edition or Microsoft SQL Server Compact Edition when developing new, non-Microsoft Access applications requiring a relational data store. These new or converted Jet applications can continue to use Jet with the intention of using Microsoft Office 2003 and earlier files (.mdb and .xls) for non-primary data storage. However, for these applications, you should plan to migrate from Jet to the 2007 Office System Driver. You can download the 2007 Office System Driver, which allows you to read from and write to pre-existing files in either Office 2003 (.mdb and .xls) or the Office 2007 (*.accdb, *.xlsm, *.xlsx and *.xlsb) file formats. IMPORTANT Please read the 2007 Office System End User License Agreement for specific usage limitations.

Note: SQL Server applications can also access the 2007 Office System, and earlier, files from SQL Server heterogeneous data connectivity and Integrations Services capabilities as well, via the 2007 Office System Driver. Additionally, 64-bit SQL Server applications can access to 32-bit Jet and 2007 Office System files by using 32-bit SQL Server Integration Services (SSIS) on 64-bit Windows.

This all pertains to the components that actually ship with Windows.  The Office team has since taken up Jet as part of Access and has come out with what they call the Access Control Entry (ACE) driver.  For more information on the ACE Drivers, you can check out this blog post which goes into details.  the ACE driver/provider is completely backwards compatible with Jet 4.0 though. 

Office 2010 will introduce a 64 bit version of Office.  With that is coming a 64 bit version of the ACE Driver/Provider which will in essence give you a 64 bit version of Jet.  The downside is that it doesn’t ship with the operating system but will be a redistributable.  There is a beta version available of this driver, as Office 2010 hasn’t been released yet.

2010 Office System Driver Beta: Data Connectivity Components
https://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en

Adam W. Saxton | Microsoft SQL Server Escalation Services

Comments

  • Anonymous
    January 21, 2010
    The comment has been removed

  • Anonymous
    April 12, 2010
    Ok fine, but it will not work in such case like this: Office 2007 x86 already installed on a  Windows 7 x64 and an application needs data from an Access db file. The Office driver can't be installed because of the Office architecture/version conflict. And then...? SQLExpress as the only real alternative on x64?

  • Anonymous
    April 30, 2010
    I had the same problem, and just fixed it. I'm running Windows 7 x64 with IIS 7.5 and ASP.NET v3.5 After noticing that the project would work correctly if I started the website from a file location instead through IIS, turns out IIS wasnt allowing the website to run in 32-bit mode, and all I had to do was change the Application Pool's Advanced Setting: Enable 32-bit Applications to true for the app pool my site was running (which for me was the DefaultAppPool). Didn't even need to rerun the aspnet_regiis -i option. See link for reference: http://stackoverflow.com/questions/1201918/the-microsoft-jet-oledb-4-0-provider-is-not-registered-on-the-local-machine

  • Anonymous
    May 10, 2010
    Thank you. We here at www.minimrp.com are loking forward to working with the ace-dao drivers. minimrp.com is a low cost inventory manager with bill of materials and other mrp-like features based on Microsoft Jet databases. We're looking forward to updating our systems to work with the Microsoft AceDao connectivity.

  • Anonymous
    May 11, 2010
    Microsoft have just released a 64-bit version of the 2010 Access Database Engine: http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en

  • Anonymous
    July 14, 2010
    Hi- I have downloaded and install the Ace OleDb on our 64 bit server - but I still have the problem using the driver : This is the error I got : Ad hoc access to OLE DB provider 'Microsoft.ACE.OLEDB.12.0' has been denied. You must access this provider through a linked server The code I used: SELECT     *  FROM   OPENDATASOURCE('Microsoft.ACE.OLEDB.12.0', 'Data Source=\nyc-clu498.ad.insidemedia.netdfsuniversalmecappdataTNSData;Extended Properties="Text;HDR=No;FMT=Delimited"')...[C3GRP_20100628.txt]

  • Anonymous
    January 09, 2011
    our niche is the transportation of copy machines all over the East coast.  Our fleet of properly equipped trucks cover New York, New Jersey and Connecticut daily. we will store the copier,   track the pending lease return date, contact your customer for the lease return paperwork .log in on http://shipwithjet.com/

  • Anonymous
    September 07, 2012
    Microsoft is using this as a sales tool, forcing the purchase and redevelopment of most probably hundreds of thousands of applications. Using forums as support mechanisms is equally unacceptable. I have a broken application (which I did not originally write) and I am stuck wading through thousands (millions?) of irrelevant search results trying to find a JET driver that will work on a web application migrated to server 2008. Might as well use open source. It's cheaper and no more difficult to work with any more.

  • Anonymous
    May 27, 2015
    This link does not work: blogs.msdn.com/.../480870.aspx.  It is referenced in the statement --  "you can check out this blog post"

  • Anonymous
    December 02, 2015
    MPORTANT Please read the 2007 Office System End User License Agreement for specific usage limitations What are those limitations? can we use it in production?