RE: Field level security

Provided Foreman_Table maintains a user id column for the foreman (i.e.
Foreman_User_Id), an SQL view may still make it easier on your users.
Something like:

CREATE VIEW onlyYou AS
(SELECT field1,field2,field4,field5
FROM Foreman_Table
WHERE USER = Foreman_User_Id)

This view would implement both field and row selection (leveraging the USER
sql special register), and assuming the preparatory work was done using
native security so foreman can only access this view and not the table
directly, it really implements both field AND row level security, which it
seems what your users are after.

Your queries could then go against this view, and you wouldn't need to
expose users to the IF/THEN/ELSE logic.

HTH, Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: RE: Field level security

Nope. The client wants to be able to maintain it herself after I finish it.
SEQUEL's scripting tool has been enhanced to allow IF/THEN/ELSE logic. I'll
just retrieve the user id, tie it to the foreman file, then tie the foreman
number to the crew.

Paul Nelson