I would like to know how to go about doing this.
I have a table ClientInfo in SQL 2k. I want the customer
service dept to be able to add new clients and search for
ones to edit. I want other groups to be able to only view
client info read-only.
1. I assume creating a webpage is probably better than
an .adp file?
2. If I do a webpage, how do I deal with the
permissions? Should I create a login table and add all
the users/pwd in there and set the level of security that
way? Or is there a way to base it off of Windows active
directory groups?
Thanks.
You can set the security with in SQL Server based on the NT users. You can
create a view that has the data that you wan the users to view and then
only give select permissions to the to those users.
In other words use teh security mechnism within SQL Server to set the
security.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks!
I use the dsnless connection string for trusted_connection
to base ithe permissions on the user.
However, the windows login box does pop up for them to
enter in username/pwd/domain.
Is there a way that sql grabs the user info automatically
and set the perms that way?
If I have a default page and links to an edit page, is
there a way to use the user info to disallow certain
people from entering that page?
Ngan
>--Original Message--
>You can set the security with in SQL Server based on the
NT users. You can
>create a view that has the data that you wan the users to
view and then
>only give select permissions to the to those users.
>In other words use teh security mechnism within SQL
Server to set the
>security.
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>
Friday, February 17, 2012
Connecting a webpage to SQL
Labels:
clientinfo,
clients,
connecting,
customerservice,
database,
dept,
microsoft,
mysql,
oracle,
server,
sql,
table,
webpage
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment