how to implement field-level security

[silverblatt]

I need to set up a list in which "A" users can only view and edit a subset of the fields in a custom list, while "B" users can veiw and edit all fields. It would also be nice if, when an "A" user creates a new list item, one of the fields that is only accessible to "B" users could be set to a pre-determined value.

I'm open to different approaches here (different views of the same list, different lists with some automated way to copy items from the one list to the other, a single view of a single list with some mechanism to enforce the restrictions outlined above, or perhaps some other approach I haven't thought of). My biggest concern is that the solution be as straightforward and simple to implement as possible. I'm an experienced VB/C#/SQL developer, but my exposure to SharePoint has been limited to setting up and customizing very simple sites via a web browser. I have absolutely no experience using SharePoint Designer, or any other SharePoint development tool, and am not sure I will have the time to learn it to complete this project.

Thanks in advance for your suggestions.

 

[gnosis13]

We installed KWiz List Form Extensions to do what you are doing (

http://kwizcom.com/ProductPage.asp?ProductID=1048&ProductSubNodeID=1049).

It works as advertised, though, we did have some performance issues with a list that had a lot of fields. For small lists it seems to work fine.

 

[shareidear]

Regarding to SharePoint field-level security, I want to tell you first that SharePoint is not reliable.
Depending on your security concerning, there are several ways you can turn to.
Give a shot to SharePoint Item Level Permission. If you do not care too much about fiel level security, maybe this helps.
Take a look at SharePoint Column View Permission and Kwizcom Permission(Mentioned above)and others. I am using the first. All of them are effective in field security, you need to pay money of it though.
Hope those things help!