ODBC "architecture mismatch" connecting to Relational View

[ghosttie]

On some computers we are completely unable to use ODBC to connect to a Relational View because we get this error:

Error: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
Code: 80004005
Source: Microsoft OLE DB Provider for ODBC Drivers

I Googled the error message and all I found was advice to use C:\Windows\SysWOW64\odbcad32.exe instead of c:\windows\system32\odbcad32.exe when configuring a 32bit DSN on a 64bit operating system, but we are already doing that.

Has anyone else had this problem, or have any ideas?

[torrie]

What application are they connecting from? I get this error when using Office 64 bit and Jade 32 bit.

ODBC is done "In Process" which means that the archiecture (64 or 32 bit) needs to be the same. Office automation for example is done Out of Process which means that a 32 bit Jade application will work with the 64 bit office.

If the client is using a 64 bit office application (or similar) then you will need to provide a 64 bit Jade client.

[ghosttie]

It's a 32bit app, but we're testing it with a .vbs script. Since the .vbs works on some computers but not others it makes me think that's not the problem.

[torrie]

Does it work on Windows 32 bit but not on windows 64 bit?

.vbs scripts are normally associated with CScript.exe or WScript.exe. This is found in the c:\windows\system32 directory and also in the c:\windows\syswow64 directory, so the executable running the script exists in a 32 or 64 bit version.

On a 64 bit OS, instead of running
cScript ABC.vbs

try explicitly pointing it at the 32 bit executable, e.g.
c:\windows\syswow64\cscript.exe ABC.vbs

This should ensure that everying involved is running as 32 bit.

[ghosttie]

I didn't know there were separate script exe's - that fixed it, thanks