These new or converted Jet applications can continue to use Jet with the intention of using Microsoft Office 2003 and earlier files (.mdb and. When developing new, non-Microsoft Access applications requiring a relational data store. Instead of Microsoft Jet, Microsoft recommends using
64 bit microsoft access database engine drivers#
Native 64-bit applications cannot communicate with the 32-bit Jet drivers running in WOW64. On 64-bit versions of Windows, 32-bit Jet runs under the Windows WOW64 subsystem. There is no 64-bit version of the Jet Database Engine, the Jet OLEDB Driver, the Jet ODBC Drivers, or Jet DAO available.
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. 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). Starting with version 2.6, MDAC no longer contains Jet components. Additionally, when you upgrade or modify existing applications, remove any dependency on these components.Īnd here is what it lists about the Jet Database Engine:
Microsoft recommends, when you develop new applications, that you avoid using these components. These components are still supported in the current release of MDAC/WDAC, but they might be removed in future releases. What does deprecated mean? Here is the excerpt from the The answer is that the windows versions won’t be 圆4 as those items are deprecated.
Windows only ships the 32 bit versions of these. We have had a number of people ask about how they can get the Jet ODBC driver/OLE DB Provider as 64 bit.
0 kommentar(er)
