adddeveloper
Programmer
We have an application with about 400 users. The way the user authenticates is via a government security card password, and each user has their own unique number...not their SSN, but like that...unique to each individual. When the user enters the application, they are all stamped as "webuser" so the DBA can see what's happening.
What we'd like to do is limit some users to "Read Only" access. We store each individuals unique number in a table so we know what database on the server they have access to, but I was wondering if via Principal or Identity I can limit them to "Select" statement against the db.....and not allow Insert/Update/Delete commands. We can put a flag in the same table which stores their name, and write a module to look for the flag....and exit the routine for a datagrid delete/update or a button which updates the db...but that means for the 20+ pages we have, and probably 10 places on each page....a lot of code.
Any ideas are welcome!
Thanks!
What we'd like to do is limit some users to "Read Only" access. We store each individuals unique number in a table so we know what database on the server they have access to, but I was wondering if via Principal or Identity I can limit them to "Select" statement against the db.....and not allow Insert/Update/Delete commands. We can put a flag in the same table which stores their name, and write a module to look for the flag....and exit the routine for a datagrid delete/update or a button which updates the db...but that means for the 20+ pages we have, and probably 10 places on each page....a lot of code.
Any ideas are welcome!
Thanks!