Re: Security role problem
- From: "Uri Dimant" <urid@xxxxxxxxxxx>
- Date: Mon, 19 Mar 2007 11:21:19 +0200
Tore
I have a security role that has the permission to run a stored procedure.
The stored procedure does a select and an update on a table. To make the
stored procedure run the security role have to be granted permission to do
select and update on the table.
Only if you use dynamic sql within a stored procedure, otherwise you need
grant EXECUTE permission on this SP
The problem occurs when I attach this role to the end user of the
database.
This means that the end user can use excel, access or any other tool to
access the table directly and do updates of the table. I do not want this.
I
would like the user to operate on the table via the stored procedure only,
not directly. How can this be fixed?
Access database has linked tables to SQL Server?
"Tore" <tgyl@xxxxxxxxxxxxx> wrote in message
news:ACA5801B-C93C-43E8-B5BE-954902E09D2F@xxxxxxxxxxxxxxxx
I have an SQL Server 2000 database with access project (.adp) front end.
I have a security role that has the permission to run a stored procedure.
The stored procedure does a select and an update on a table. To make the
stored procedure run the security role have to be granted permission to do
select and update on the table.
The problem occurs when I attach this role to the end user of the
database.
This means that the end user can use excel, access or any other tool to
access the table directly and do updates of the table. I do not want this.
I
would like the user to operate on the table via the stored procedure only,
not directly. How can this be fixed?
Regards
Tore
.
- Prev by Date: Re: File Ownership failing for Domain Accounts
- Next by Date: Re: Cannot view logins from syslogins, sys.server_principals, sys.server_role_members in SQL 2005
- Previous by thread: Re: Error 18456 Severity 14 State 16
- Next by thread: Security role problem
- Index(es):
Relevant Pages
|
|
