Win7 64-bit Database Connectivity issue: The architecture mismatch between the driver and the application in the specified DSN

The workaround for "the architecture mismatch between the driver and the application in the specified DSN" is an exception when connecting programs and databases via ODBC/JDBC

Native : 64-bit win7,64-bit JDK, 32-bit myeclipse for web experiments after a problem with either Access or SQL Server connection database, I finally understand why the Java experiment did not connect to the Access database but SQL Server is no problem, now the perfect solution, haha!

Reason:

The 64-bit Win7 OS ODBC version defaults to 64-bit (SQL Server data source is also 64-bit) and requires 64-bit JDK and 64-bit Office (access). Use myeclipse should also correspond to 64-bit MyEclipse version

For 32-bit myeclipse, the database should be connected to a 32-bit ODBC data source (32-bit established SQL Server data source)

Workaround:X:\Windows\SysWOW64\odbcad32.exeFor example:Go to the C:/windows/syswow64 folder, open the Odbcad.exe, and open the 32-bit version of ODBCUse this to create a system DSN for ODBC to connect to SQL Server or Access, the access suffix should be MDB Note that the JDK path should be set to the same path as the 32-bit JDK, and the 32-bit version should be used with MyEclipse MyEclipseNote: The 64-bit version of the location: C:\windows\system32\odbcad32.exe32-bit version of the location: C:\windows\sysWOW64\odbcad32.exe
Once the database is set up and running successfully, the JDK is changed back to 64 bits as if it had no effect on the database.

Win7 64-bit Database Connectivity issue: The architecture mismatch between the driver and the application in the specified DSN