Symptoms
A 64-bit version of the Microsoft Windows operating system includes
the following versions of the Microsoft Open Database Connectivity
(ODBC) Data Source Administrator tool (Odbcad32.exe):
The 32-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\SysWoW64 folder.
The 64-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\System32 folder.
The Odbcad32.exe file displays the following types of data source
names (DSNs):
Symptom 1
The 32-bit version of the ODBC Administrator tool displays 32-bit
system DSNs, 32-bit user DSNs, and 64-bit user DSNs. The 64-bit
version of the ODBC Administrator tool displays 64-bit system DSNs,
32-bit user DSNs, and 64-bit user DSNs.
Symptom 2
The SQLDataSources function returns all versions of user DSNs,
regardless of the architecture of the application. The
SQLDataSources function that is called in a 32-bit application returns only system DSNs for 32-bit drivers but returns user DSNs for
both 32-bit drivers and 64-bit drivers. Similarly, the
SQLDataSources function that is called in a 64-bit application returns only system DSNs for 64-bit drivers but returns user DSNs for
both 32-bit drivers and 64-bit drivers. Therefore, if the application
makes a connection by using a user DSN that is returned from the
SQLDataSources function, you may receive the following error message:
Data source name not found and no default driver specified
For example, consider the following scenario. You create a user DSN
for the 32-bit driver "Microsoft Access Driver (*.mdb)." This driver
does not have a corresponding 64-bit version. The SQLDataSources
function that is called in a 64-bit application returns this 32-bit
user DSN. However, if you make a connection through this 32-bit user
DSN, you receive the error message that is mentioned earlier in this
section
Cause
The user DSNs are stored under the following registry subkey:
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI
Registry redirection is not enabled for this registry subkey.
Therefore, user DSNs are visible in both the 32-bit and 64-bit
versions of the ODBC Administrator tool.
Resolution
To maintain backward compatibility, no resolution for this problem is
currently available.
Workaround
To work around this problem, use the appropriate version of the ODBC
Administrator tool. If you build and then run an application as a
32-bit application on a 64-bit operating system, you must create the
ODBC data source by using the ODBC Administrator tool in
%windir%\SysWOW64\odbcad32.exe. To indicate the type of DSN, you can
add "_32" to the 32-bit user DSNs and "_64" to the 64-bit user DSNs.
More Information
The 64-bit ODBC Administrator tool can be invoked from Control Panel
to manage user DSNs and system DSNs that are used by 64-bit processes.
On a 64-bit operating system, the 32-bit ODBC Administrator tool is
used for Windows on Windows 64 (WOW64) processes. You must directly
invoke the 32-bit ODBC Administrator tool from the SysWoW64 folder.
You can use the 32-bit ODBC Administrator tool to manage user DSNs and
system DSNs that are used by WOW64 processes.
System DSNs are stored in the following registry subkey:
HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI
Registry redirection is enabled for this registry subkey. Therefore,
system DSNs for 32-bit drivers and for 64-bit drivers are separated.
The 64-bit ODBC Administrator tool does not display system DSNs that
are created by the 32-bit ODBC Administrator tool. Similarly, the
32-bit ODBC Administrator tool does not display system DSNs that are
created by the 64-bit ODBC Administrator tool. Also, the 64-bit ODBC
Administrator tool does not display system DSNs that use 32-bit
drivers. Similarly, the 32-bit ODBC Administrator tool does not
display system DSNs that use 64-bit drivers.
User DSNs are stored in the following registry subkey:
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI
Registry redirection is not enabled for this registry subkey.
Therefore, both ODBC Administrator tools display all user DSNs.
For more information about registry redirection, visit the following
Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/aa384232.aspx
Best Answer
This per se won't cause you an issue, you have to install the 64-bit version of Microsoft Office 2010. You have to have a good reason for installing the 64-bit version, Microsoft installs the 32-bit version by default on 64-bit machines for a reason - stuff stops working.
No, but for connectivity within Office applications just install the 64-bit version of ACE and make sure your connection strings reference
Microsoft Access Driver (*.mdb, *.accdb).SQL Server and Oracle and a whole host of other common RDBMS' have 64-bit ODBC drivers, so I can't see how between 64-bit ACE and SQL Native Client/ODAC you can't connect to something.
If it still doesn't work, there's a general purpose mechanism for "proxying" x64 -> x86 via SQL Server linked servers in this forum post. Replace
Microsoft.Jet.OLEDB.4.0and other settings (to make it a linked server via ODBC, rather than ODBC) with your ODBC provider as appropriate.