I believe V5R1 introduced the "Read" trigger event.  Still, using a trigger
to enforce security seems a little out of place.  Trigger determines this
record should not be available, pops an exception message to the program,
program blows up unless you've written appropriate error handling into your
app. I would probably go with a logical that omits the FERPA records......

Eric DeLong
Sally Beauty Company
MIS-Sr. Programmer/Analyst
940-898-7863 or ext. 1863

-----Original Message-----
From: Pete Hall []
Sent: Wednesday, January 23, 2002 7:14 PM
Subject: Re: Use of a trigger...? is this areasonable?

At 11:20 01/23/2002, Booth Martin wrote:
>Here's the deal:  our name and address file has a field in their for FERPA.
>If its marked then the name can not be listed or generally distributed
>without that person's written permission.   This has worked fine for years
>when we only accessed the information with our RPG programs.
>Now though we have users with Query and other methods of accessing the
>and these users just ignore the FERPA field.  The results are labelled
>Trouble waitng to happen".
>What ways would you folks offer as ways to prevent access to that record if
>FERPA is chosen?  (I'm thinking this is a question all of us are facing

Since you are trying to prevent read access to the data, a trigger will not
be helpful. There is no such thing as a "read" trigger, just Insert, Update
and Delete.

Possibly you could use a view that excludes records with the FERPA flag
set, and restrict direct access to the data.

Pete Hall

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email:
To subscribe, unsubscribe, or change list options,
or email:
Before posting, please take a moment to review the archives

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 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.