>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 H Leverich III
Tech Software
(516)627-3800 x11

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.