MS Access macro no longer works when upgraded to 64 bit

marcoslopez · 2022-07-28T15:33:59.000Z

I have a MS Access accdb file with a form that calls a macro. The macro calls a OpenQuery in Edit Mode. This works fine with 32-bit Access but breaks when upgraded to 64-bit.

I dont understand what needs to be changed to make it work under 64-bit Access.

I see a couple of ODBC entries in Linked table manager that look like this:

DSN=SOTAMAS90;Description=MAS 90 4.0 ODBC Driver;Directory=\10.5.5.160\Sage\Sage 100 2014\MAS90

From examine the registry, the user does not have the SAGE driver installed on his PC. Can someone explain how this works, and whats needed to make it work under 64-bit?

Thanks

BadAndyG · 2022-07-28T16:48:29.000Z

You need to setup a 64 bit ODBC on the control panel.

gregseales2 · 2022-07-28T17:33:21.000Z

I ended up just installing 32bit version of Office 365 instead of 64bit for using MS Access with ODBC links to external data like Sage and others. I have a couple dozen external application for reporting and other functions I did not feel like sorting all the issues the 64bit casued.

marcoslopez · 2022-07-28T18:18:34.000Z

Both 32-bit and 64-bit ODBC User DSN connect fine

Copied the connection string from ODBC to Access Linked table manager

DSN=SOTAMAS90;Description=MAS 90 4.0 ODBC Driver;Directory=\10.5.5.160\Sage\Sage 100 2014\MAS90;Prefix=\10.5.5.160\Sage\Sage 100 2014\MAS90\SY, \10.5.5.160\Sage\Sage 100 2014\MAS90==;ViewDLL=\10.5.5.160\Sage\Sage 100 2014\MAS90\HOME;CacheSize=4;DirtyReads=1;BurstMode=1;StripTrailingSpaces=1;SERVER=NotTheServer

but get Data source name not found

Data source is there, since I copied and paste

marcoslopez · 2022-07-28T18:29:01.000Z

I think its working. added to system DSN