RE: Need to restrict User at Record level in file (Is it possible)

The problem with this is you then end up having multiple logical files out

there with different security. So if you have 100 branches you end up
with 100 LFs against that physical (or more if your keen on different
sorting criteria). Think: Design for growth.

Just an idea, but if the underlying file(s) have a user profile column in
them, you could get away with one SQL view. This view would take advantage
of the special SQL register USER and look something like this:

SELECT *
FROM underlyingTable
WHERE userProfileColumn = USER;

All users can be authorized and target this view alone, and record level
security would be enforced.

HTH, Elvis

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


-----Original Message-----
Subject: Re: Need to restrict User at Record level in file (Is it possible)