Re: Use of a trigger...? is this areasonable?

[Pete Hall <pbhall@xxxxxxxxxx>]

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 file,
>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
>lately)


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
pbhall@execpc.com
http://www.execpc.com/~pbhall/