Re: [MSAccessProfessionals] Connection to SQL with saved User and Password

Hi Doyce,

I'm confused why a "service" account would be used. I have typically seen service accounts used when one system needs to connect to another such as cross SQL Server or some software collecting data that needs automation to connect to SQL Server. Our SQL admins have always encouraged us to create (or request creation) of AD security groups and adding individuals to the groups. The AD group is then granted specific rights within the SQL database.

Regards,

Duane

---

From: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io> on behalf of Doyce Winberry <doyce.winberry@xpo.com>
Sent: Thursday, June 2, 2022 7:48 AM
To: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io>
Subject: [MSAccessProfessionals] Connection to SQL with saved User and Password

 

Hello everyone. I'm using Access 2016 and have a DB that connects to some SQL server tables. Lately my corporate DB team has said we are not Sarbanes Oxley compliant because individual users have write rights to the SQL tables so they propose that we use a "service account" to connect to the SQL tables instead of individual accounts. When they remove the write rights from my individual accounts the DB breaks because it needs to write to the SQL tables. I'm using an ODBC connection setup as a system DSN to connect to the SQL tables. When I change the DSN to use the service account they want me to use, it does not remember the password. I'm not supposed to share the password with the users. So how can I connect to the SQL tables with the service account and password and have the DB "remember" the password. I've found examples of connection strings with userID and passwords but don't know where to put them in the DB. 
Thanks in advance.
Doyce Winberry