Share via

Access returning incorrect connection string after Office update version 2312

Anonymous
2024-01-05T19:35:13+00:00

After Office update version 2312 that was released yesterday Jan 4, 2024, MS Access TableDef.Connect is returning the connection string with a missing semicolon.

ODBCDRIVER=SQL Server;SERVER=Server01\SQLEXPRESS2008R2;UID=sa;PWD=Password;APP=Microsoft Office;DATABASE=LauDatabase

The MS Access that is not updated to version 2312 is returning this with TableDef.Connect

ODBC;DRIVER=SQL Server;SERVER=Server01\SQLEXPRESS2008R2;UID=sa;PWD=Password;APP=Microsoft Office;DATABASE=LauDatabase

This seems to be a bug that was introduced in Office update version 2312. We have multiple customers with this issue. There does not seem to be an issue with the odbc connection, the link table opens fine without any issues. I have tried recreating the DSN to sql server without any luck. Here is the function that returns the connection of a table using TableDef.

Public Function TestGetConnectionString() As String
   
    Dim db As DAO.Database
    Set db = CurrentDb
   
    Dim td As TableDef
    Set td = db.TableDefs("tblSetup")
    TestGetConnectionString = td.Connect

End Function

Microsoft 365 and Office | Access | For business | 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 No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2024-01-09T11:32:01+00:00

    Hi,

    I've updated the AFo article with the information that today's new Current Channel version 2312 build 17126.20132 seems to fix the bug according to our first test.

    Servus
    Karl
    ****************
    Access Forever
    Access News
    Access DevCon
    Access-Entwickler-Konferenz AEK

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. George Hepworth 22,855 Reputation points Volunteer Moderator
    2024-01-05T19:53:16+00:00

    This bug was recently identified and reported to the Access team at Microsoft. and is being investigated.Look for an update on AccessForEver.org in the near future when it is pinned down better and we can get it written up .

    A workaround would be to manually edit the connection string(s) to restore the missing semi-colon.

    Replace(Currentdb.Tabledefs("YourTableNameGoesHere").Connect,"ODBCDRIVER=","ODBC;DRIVER=")

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-06T13:03:41+00:00

    Hi,

    The AFo article documenting the bug and the current status is now online.

    Servus
    Karl
    ****************
    Access Forever
    Access News
    Access DevCon
    Access-Entwickler-Konferenz AEK

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-01-05T20:01:11+00:00

    Thanks for the reply.

    Was this answer helpful?

    0 comments No comments