I have a SQL Server database with an Access front end. I will install the client on each user's PC. Unfortunately, there may be instances when more than one user may use the same PC to access the database. The users can fit into one of 4 roles (with different access levels).
I'd like to set up the data link properties (in Access) to log in with a generic ID or access level (read only). Maybe I can use an application role? If I do not do this, and a user does not log in each time he/she accesses the database, one could potentially be logged in as the previous user. Once a user opens the database, I'd like to set up a prompt for the actual user ID & Password.
My questions are two-fold:
1. Is it better to use a generic ID just to establish the server connection or should I use an application role? If so, what's the best way to set up the app role?
2. Once Access is opened, what is the best way to prompt the user for their ID & Password (and authenticate through SQL Server)?
Thanks in advance,
H. Barnes
I'd like to set up the data link properties (in Access) to log in with a generic ID or access level (read only). Maybe I can use an application role? If I do not do this, and a user does not log in each time he/she accesses the database, one could potentially be logged in as the previous user. Once a user opens the database, I'd like to set up a prompt for the actual user ID & Password.
My questions are two-fold:
1. Is it better to use a generic ID just to establish the server connection or should I use an application role? If so, what's the best way to set up the app role?
2. Once Access is opened, what is the best way to prompt the user for their ID & Password (and authenticate through SQL Server)?
Thanks in advance,
H. Barnes