>Hallo,
>in an database should every field action LIKE INSERT,UPDATE and SELECT
>assign to an User or an Usergroup.
>e.g.
>User A could insert in the field "street"
>USER B could not Update the field "street" etc.
>
>We think about an validation Object in the Middle tier.
>Any links to pattern or articles or any Ideas or suggestions ?
>
>tia
>achim

I don't know of a particular design pattern that covers this scenario, but there are several patterns that you could use to implement such checking.

This is not really a middle tier issue either, since it depends entirely on the current user and the form in which they are working - so it's a Presentation Tier issue.

I would do this by setting up a set of control classes which have the ability to enable/disable themselves depending on some property. Then, when each form is activated loop through the controls on the form, check the current user's rights and set the control property accordingly.

Any help?