SQL server does not seem to know who is in an AD group when the connection comes from Access ODBC

[KRAccessIssues]

We are running an older Access application. ODBC connections are set up and individual AD user accounts have access to the data on the sql server. We set up new AD groups for these individuals with the same access and they get failed odbc connections. If I put the user's AD account back in SQL Server it works fine. Does anyone know if this should work? The AD Group through Access to SQL? It seems the group member is not making it to SQL. Thank you.

[Gicu]

And the ODBC connection in Access uses the right (Windows) authentication, right? Can you inspect the connection string (open any linked table in design view and go to properties or look into the Connect field of the msysObjects system table) to see if everything looks OK?

Cheers,

[NoellaG]

If you have created new Accounts on the SQL server, you need to remove the database users and create new users with the new accounts because the old PID's don't match anymore.

[KRAccessIssues]

The ODBC connection in Access is using Windows Authentication. We are trying to clean up our sql logins so we created groups. The ADuser account Domain\userA is in the AD group Domain\SQLUsers with the appropriate rights to the sql db's. When we remove the individual account Domain\userA from SQL Server logins the ODBC connection fails even though the group the user belongs to is correct. It makes no sense.