Server M-Files 64bits access ODBC

Hi JeromeLam, the problem with ODBC connection to access under 64-bit server is that the ODBC driver for Access was only at 32-bit
Until now the only solution that I know to this kind of problem was to use Program that was compiled to 32-bit to correctly handle calls to 32-bit ODBC drivers even if they are installed in 64-bit - that mean that you have to install the 32-bit version of M-Files Server so it can call into correctly 32-bit version of the ODBC drivers for Access...

But right now, maybe, another solution is comming (but I haven't tested) - with the release of Office2010 Microsoft may has released OLEDB ODBC Driver for 64-bit... I try to find it on the web but I'm not sure if this is the correct download:
http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en
Let's try it with the 64-bit installation (I haven't one ready to test, sorry) and you can try-it, to solve your problem I think you have to correctly configure the connectionstring like those reportend on the download page (see quote text)

2.If you are an application developer using OLEDB, set the Provider argument of the ConnectionString property to “Microsoft.ACE.OLEDB.12.0”
◦If you are connecting to Microsoft Office Excel data, add “Excel 14.0” to the Extended Properties of the OLEDB connection string.
3.If you are application developer using ODBC to connect to Microsoft Office Access data, set the Connection String to “Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=path to mdb/accdb file”
4.If you are application developer using ODBC to connect to Microsoft Office Excel data, set the Connection String to “Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};DBQ=path to xls/xlsx/xlsm/xlsb file”

Hope this may help
Lele (codbit)

Hi JeromeLam, the problem with ODBC connection to access under 64-bit server is that the ODBC driver for Access was only at 32-bit
Until now the only solution that I know to this kind of problem was to use Program that was compiled to 32-bit to correctly handle calls to 32-bit ODBC drivers even if they are installed in 64-bit - that mean that you have to install the 32-bit version of M-Files Server so it can call into correctly 32-bit version of the ODBC drivers for Access...

But right now, maybe, another solution is comming (but I haven't tested) - with the release of Office2010 Microsoft may has released OLEDB ODBC Driver for 64-bit... I try to find it on the web but I'm not sure if this is the correct download:
http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en
Let's try it with the 64-bit installation (I haven't one ready to test, sorry) and you can try-it, to solve your problem I think you have to correctly configure the connectionstring like those reportend on the download page (see quote text)

2.If you are an application developer using OLEDB, set the Provider argument of the ConnectionString property to “Microsoft.ACE.OLEDB.12.0”
◦If you are connecting to Microsoft Office Excel data, add “Excel 14.0” to the Extended Properties of the OLEDB connection string.
3.If you are application developer using ODBC to connect to Microsoft Office Access data, set the Connection String to “Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=path to mdb/accdb file”
4.If you are application developer using ODBC to connect to Microsoft Office Excel data, set the Connection String to “Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};DBQ=path to xls/xlsx/xlsm/xlsb file”

Hope this may help
Lele (codbit)