Actually *read *before is not allowed. But, after some testing the *read *after does actually happen before the data is passed to the user. I haven't tried changing the field. If I get a minute I will. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin firstname.lastname@example.org Sent by: To: email@example.com midrange-l-admin@mi cc: drange.com Fax to: Subject: RE: Use of a trigger...? is this areasonable? 01/24/2002 08:59 PM Please respond to midrange-l Booth, I haven't seen the fine details for V5R1 *read trigger addition. However, it occurred to me that _IF_ a *read *before could alter the input buffer sent to the requestor this could help your situation. e.g. add *read *before trigger, perform business rules, if the requestor not authorised or whatever then, change sensitive fields to "classified" or blanks or zeros or whatever. As this is read only it won't affect the real file. the $64k question here of course is whether the trigger can alter what the requestor sees on *read triggers? _______________________________________________________________ Regards, Rod Orr _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-Lfirstname.lastname@example.org Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.