Not sure if this is the right place for this question (Perhaps SuperUser), but I'm sure there are some Access gurus here on ServerFault.
Anyway, we support some legacy MS Access apps and recently a user was able to change some information in our database. NOT GOOD! It should be read only.
MS Access is using a Trusted Connection and the user is part of a Windows Group in SQL Server that is only a DB Reader.
Is there a list of Gotchas when implementing Windows Users on SQL Server that we've missed?
The only clue that we had is that we only allow connections on a non-standard port.
How did you add the users in?
You should probably setup a group for people that need to access the data. Then setup them with security to allow for Read-Only on just the tables that are needed.
If you don't have specific roles setup for users, you made them added them as the database owner or administrator.
The Trusted Connection only specifies Windows Users instead of SQL specific logins.