Re: Prevent a record from being written using a trigger program.

[Luis Rodriguez <luisro58@xxxxxxxxx>]

Terry,

Just a not very thought-out idea but, What happens if you define an AFTER
insert trigger and, if you don't like the record, just delete it?

HTH,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Wed, Aug 31, 2011 at 11:10 AM, Terry Anderson <TAnderson@xxxxxxxxx>wrote:

> Greetings List,
> We use a third party package to maintain our customer master file.
> Corporate has decided to standardize on customer numbers across our 18
> divisions.  They want a way to prevent the divisions from creating a
> customer record that uses a
> non-sanctioned customer number.  I do not want to modify the third party
> code if I can help it.
>
> I have used trigger programs in the past to track changes to a file but
> is there a way to use one to prevent a record from writing to a file?
> If so, does someone have an example of how to do this they would be
> willing to share?
>
>
> Thanks,
>
>
> Terry Anderson
> Programming Manager
> Grede LLC.
> Switchboard 1.251.867.5481 ext 212
> Direct Line 1.251.809.2312
> Fax 251.867.0525
> Cell  1.251.363.4975
>
>
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.