MS Access connecting to SQL using ODBC driver.

M

MatthewM23

Bit poster
This is a very specific scenario, but it is one of the primary use cases for our business machines. For years, we have used parallels to run Access on Intel Macs to query a local server that has customer information on it. For years, the solution has worked perfectly and allowed us to continue using a database that someone built for us decades ago while taking advantage of macOS. I bought a M1 iMac to deploy and I'm about to have to return it.

I have successfully installed Windows 11, and all the other software I need on it. Our business uses Sage for our bookkeeping, and I got it working perfectly. I installed Office with Access and the Microsoft ODBC Driver 13 needed to speak to the SQL server. My problem arises when I go to actually run the Access file that talks to the SQL server. Access shuts down every time with no warning or error. If I can't get it up and running, then I'm going to have to return it because that is its primary purpose.

I have tried other versions of the ODBC driver and other versions of Access (both the full and runtime versions) in various combinations and the same thing happens every single time. I have also tried the compatibility troubleshooter as well.

Has anybody had any similar issues? I know I'm talking very edge case use here.
Thanks!
 
Further investigation reveals the crash is caused by the Access database. Specifically, the designer used ActiveX in Visual Basic and when the app attempts to use ADODB in the Microsoft ActiveX Data Objects 6.1 Library (msador15.dll) the app crashes. Take out that reference and the app doesn't crash but then it doesn't compile correctly. At least from there I can use some of the functionality and determine that it can access the SQL server just fine.
So the problem most likely stems from the fact that Microsoft has a buggy ActiveX library. Now we're getting into Visual Basic, but does anyone know of a workaround?
 
You must log in or register to reply here.
Back
Top