Column-level security 1

[Niv3k]

I have two general security practices, read-only and read-write. But I have ONE table that has ONE column that I don't want all the read-write people changing it.

So I set up the read-only group, and that works fine. But when I set up the read-write group, I left off permissions for that table. I then set up two more groups, one with "SELECT" access to that column, and one with "SELECT" and "UPDATE".

The problem is, it doesn't seem to want to allow updates from the people who have the ability. I am using 2000.

Kevin

 

[RickCole]

It's difficult to say what might be wrong here from the current information. Can you script up the table permissions and post the script here as this might help to pin point what is going on.

Just my personal opinion here but I would have a view of the table minus the column which you do not want updating. Just then give permissions via the view instead. I find this easier to manage and much more flexible.

Rick.

 

[tlbroadbent]

I agree with Rick. Although you can set permissions on columns, it is much easier to administer a view. Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.

 

[Niv3k]

Well, I did the view method, and it works. I think I will try to play around with the columns on my test machine next week, though. If it turns out to be too much of a problem, I'll just never implement it.

Thanks, guys...
Kevin