Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2025
    Posts
    1

    ODBC--connection to 'ODBC DRiver 17 SQL Server [server]' failed.

    I have been trying to solve this issue for a few days. I'm hoping someone can confirm that I'm not bonkers...or maybe I am.

    I am not in the IT department...I'm just part of the team who uses MS Access.

    Project: Data migration from MS Access to onprem SQL test Server.
    Goal: Scalability, Power BI, yada yada yada...all the goods.



    I'm going to try to run through this the way it happened.

    on Prem SQL Server
    Test database created.
    Server security set for Active Directory domain name\Security Group [domain\group]
    Test db set for domain\group
    GRANT SELECT UPDATE INSERT DELETE to [dbo.[table]] given to [domain\group]

    MS Access
    on a shared drive
    we have to tell each other when we're in/out.
    feeds into several excel spreadsheets that we can edit using Power Query

    onprem SQL Server
    Server security set for Active Directory domain name\Security Group [domain\group]
    Test db set for domain\group
    GRANT SELECT UPDATE INSERT DELETE to [dbo.[table]] given to [domain\group]

    MS Access
    connectin string set to allow windows authentication
    copied db
    new data source
    create links to onprem SQL using DSN-less for Ms Access data entry direct into SQL.

    save save save...all saved.

    Open MS Access > some form
    Create a record
    save
    SELECT [column with new info]

    Totally worked!

    EXCEPT...when my team tries to open that same MS Access file on the shared drive, or anywhere they copy it to, they get this error:
    ODBC--connection to 'ODBC Driver 17 SQL Server [server]' failed.

    I have asked IT support to fix the error and I've been told that they don't allow access to db. Right, but this is access to my data, on a test database, on a solution that by all accounts, is very typical.

    I just wanted to test the DSN-less on a test server on a test db. What am I doing wrong that this isn't viable and why is my team not able to access? How should the ODBC--connection to 'ODBC DRiver 17 SQL Server [server]' failed be addressed? What about a service account? I am using a connection string.

  2. #2
    Minty is offline VIP
    Windows 11 Office 365
    Join Date
    Sep 2017
    Location
    UK - Wiltshire
    Posts
    3,157
    Do they have 'ODBC Driver 17 SQL Server' installed on their machines?

    It's not installed as a default with anything, they would need it installed manually on every PC.
    DLookup Syntax and others http://access.mvps.org/access/general/gen0018.htm
    Please use the star below the post to say thanks if we have helped !
    ↓↓ It's down here ↓↓

  3. #3
    CJ_London is online now VIP
    Windows 10 Access 2010 32bit
    Join Date
    Mar 2015
    Posts
    11,927
    MS Access
    on a shared drive
    we have to tell each other when we're in/out.
    risky strategy

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 3
    Last Post: 09-30-2021, 11:53 AM
  2. Replies: 5
    Last Post: 03-30-2020, 05:31 PM
  3. Replies: 2
    Last Post: 02-14-2020, 04:10 AM
  4. Replies: 1
    Last Post: 03-02-2015, 09:44 AM
  5. Connection to SQL Server ODBC Failed
    By Historypaul in forum SQL Server
    Replies: 2
    Last Post: 01-05-2015, 01:50 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums