RE: field level security - (Was Use of a trigger...? ....)

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

>From: Christian ENRIQUEZ [mailto:christian@asp-re.com]
>You can basicaly remove fields, protect them, remove function keys,

Ah, but screen-level security misses the point. IIRC, the original question
dealt with users downloading the file, how does your product prevent that
level of access? You could, of course, revoke everyone's access to the files
and only access the file through programs that adopt, but most system
weren't designed for that.

As far as the trigger idea goes, I think in this case I'd replace the values
with "Protected by FERPA" or something to that effect rather than *LOVAL.
That way users know there is data, but they aren't allowed to see it. Of
course if you implement this read trigger how will the programs that ARE
allowed access to the data see it? You'll need some way of saying "This job
is allowed access", perhaps a dataarea in QTEMP, or a Job Switch (gulp!<G>)
or ?????

-Walden


------------
Walden H Leverich III
President
Tech Software
(516)627-3800 x11
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com