Hi slim17 , if you are using a DSN to connect to the file, then you need to use C:\Windows\SysWOW64\odbcad32.exe to create/configure it. This is the 32-bit version.
Hi Mike_James
Previously we have installed driver locally. It is creating folder C:\MYOBODBCAU10 after installation.
Then we are connecting in C# using an ODBC connection object using MYOB driver connection string to database. This has created connection without having to manually creating DSN in Windows control panel.
Connectionstring was like this:
{MYOAU1001};TYPE=MYOB;ACCESS_TYPE=READ_WRITE;DRIVER_COMPLETION=DRIVER_PROMPT;SQL_LOGIN_TIMEOUT=30;SUPPRESS_WARNINGS=TRUE;NETWORK_PROTOCOL=TCPIP;HOST_EXE_PATH=C:\Premier19\Myobp.exe;UID=x;PWD=y;Database=C:\Premier19\DB.myo;KEY=z;
Does this make sense?
Hi slim17
You may need to re-install the MYOBODBC driver now that you have upgraded your computer. I use ODBC in similar manner to what you have described. I run this on a 64 bit Windows OS - the 64 bit system is not the issue, it is that the 64 bit system cannot find the driver MYOBAU1001 - reinstalling this might help recreate the relevant registry settings.
Regards
Gavin
Hi gavin12345 ,
Wondering if you can offer any assistance.... we use ODBC on good old enterprise 19.7 and recently had to set up on a 64 bit machine (previously running on a 32 bit). I too get the "The specified DSN contains an architecture mismatch between the Driver and Application" message when running our interface program. I set up the DSN from the 32bit ..windows/SysWOW64/odbcad32 and the test connection indicates no problems but still get the architecture mismatch error?, I'm pulling my hair out and i'm guessing it's something simple.
Regards,
Sam
