From the Data Access Technologies Road Map
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
http://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
This means you can install the 32 bit versions but your applications must also be 32 bit to access them.
If you want to Configure the ODBC setting from the windows management tool you'll need to use the 32 bit version located at %systemdrive%\Windows\SysWoW64\Odbcad32.exe.