Share via

Issue connecting to SQL Server with MS Access on Insider Preview version 2312 build 17126.20078

Anonymous
2023-12-18T15:17:52+00:00

Getting following error with Access with Office 365 using the Insider Preview version 2312 build 17126.20078.

(-2147024809) Keyword not supported: 'odbcdriver'.

Tried restarting the pc, and recreating the DSN without any luck.

Microsoft 365 Insider | Access | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-12-18T20:33:44+00:00

    Hello! Lau12345

    Thank you for posting in Microsoft Community

    As per checking the information shared that you are having trouble connecting to SQL server with the use of Microsoft Access on Insider preview version. Based on the description it seems to me that your concern is out of my field of expertise as I can only do basic troubleshooting steps for Microsoft Office programs, OneDrive, and Outlook.

    We will leave the thread open in case some Volunteer Moderatos or other community want to join in.

    You may also share your concern here in: Questions - Microsoft Q&A

    Thank you,

    Vince

    Microsoft Community Moderator

    0 comments
  2. Anonymous
    2024-01-08T15:45:51+00:00

    An issue here that maybe relates to this. Apparently the 'Connect' property of the 'TableDefs' object now returns an incorrect value.

    Depending on how the returned value is later used in the VBA code, error messages I get are:

    • Runtime error '3305': invalid connection string in pass-through query
    • Runtime error '3170': could not find installable ISAM

    In VBA for example: CurrentDb.TableDefs("TABLENAME").Connect

    In version 2302 this returns:

    ODBC;DRIVER=ODBC Driver 18 for SQL Server;SERVER=.... etc.

    In version 2312 this returns:

    ODBCDRIVER=ODBC Driver 18 for SQL Server;SERVER=... etc.

    Apparently the first semicolon is missing in the return value, the remainder of the connect property is identical and appears OK.

    0 comments