Grant and Revoke on a column

I am trying to give limited privileges to a login account on a table, but it
doesn't seem to work. I have a link table in Access 97 and my SQL server is
version 7. Some columns are supposed to be read only and some columns are
supposed to be read-only.
I use the script below
revoke all privileges on stores to shipdirect1
grant update on stores(creditlimit) to shipdirect1
What am I doing wrong?Arne,
SQL Server does not support column level permissions. Even if it did it is
doubtful Access supports it. You will be better off setting up a view with
the permitted columns and granting permissions to it to the user.
Ilya
"Arne" <Arne@.discussions.microsoft.com> wrote in message
news:CC4D4275-A5EC-4C30-B875-8A5CB2626C65@.microsoft.com...
> I am trying to give limited privileges to a login account on a table, but
it
> doesn't seem to work. I have a link table in Access 97 and my SQL server
is
> version 7. Some columns are supposed to be read only and some columns are
> supposed to be read-only.
> I use the script below
> revoke all privileges on stores to shipdirect1
> grant update on stores(creditlimit) to shipdirect1
> What am I doing wrong?
>|||SQL Server 7.0 that is.
"Ilya Margolin" <ilya_no_spam_@.unapen.com> wrote in message
news:OdYOh6GFFHA.2756@.TK2MSFTNGP15.phx.gbl...
> Arne,
> SQL Server does not support column level permissions. Even if it did it is
> doubtful Access supports it. You will be better off setting up a view with
> the permitted columns and granting permissions to it to the user.
> Ilya
> "Arne" <Arne@.discussions.microsoft.com> wrote in message
> news:CC4D4275-A5EC-4C30-B875-8A5CB2626C65@.microsoft.com...
but
> it
> is
are
>|||Actually, SQL Server DOES support column-level permissions and has done so
since the earliest version.
The problem is probably related to linking to the Access table, if access
doesn't support this.
How do you know it doesn't work? Are you getting an error? What does it say?
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Ilya Margolin" <ilya_no_spam_@.unapen.com> wrote in message
news:OdYOh6GFFHA.2756@.TK2MSFTNGP15.phx.gbl...
> Arne,
> SQL Server does not support column level permissions. Even if it did it is
> doubtful Access supports it. You will be better off setting up a view with
> the permitted columns and granting permissions to it to the user.
> Ilya
> "Arne" <Arne@.discussions.microsoft.com> wrote in message
> news:CC4D4275-A5EC-4C30-B875-8A5CB2626C65@.microsoft.com...
> it
> is
>|||Kalen,
When I update a column that is supposed to be read-only I don't the
exception that I expected.
However I found some MS Access properties that solved the problem for me.
Arne.
"Kalen Delaney" wrote:

> Actually, SQL Server DOES support column-level permissions and has done so
> since the earliest version.
> The problem is probably related to linking to the Access table, if access
> doesn't support this.
> How do you know it doesn't work? Are you getting an error? What does it sa
y?
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Ilya Margolin" <ilya_no_spam_@.unapen.com> wrote in message
> news:OdYOh6GFFHA.2756@.TK2MSFTNGP15.phx.gbl...
>
>