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

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I think deleting the record would be a bad idea.  Sure, you won't have
the bad number in the customer table, but records with that now
non-existent customer number could still be added other files.

I'd run a test to see if the program handles the write failure
correctly....if so, you could go back to the original idea of having
the trigger throw and exception...

Charles

On Fri, Sep 2, 2011 at 2:18 PM, Terry Anderson <TAnderson@xxxxxxxxx> wrote:
> Booth,
> I don't think that would work in this instance.  The division still
> needs to know the customer number is so they can the  create packing
> slip, bill of lading and ASN.  The third party program also updates
> other files like the ship to master.
>
> I think the best way for me to go, would be the suggestion of letting
> the third party program update the files then use my trigger to delete
> the records if the customer number the user entered was not in a file of
> corporate sanctioned numbers.  I would also need to send a message or
> pop up a window letting the user know what happened.
>
> Thanks to everyone who responded!  I get a lot of good ideas and things
> to think about from this list!
>
>
>
>
> 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
>
>
>
> ----------------------------------------------------------------------
>
> message: 1
> date: Thu, 01 Sep 2011 11:59:55 -0500
> from: Booth Martin <booth@xxxxxxxxxxxx>
> subject: Re: Prevent a record from being written using a trigger
>        program.
>
> Have you considered writing a small program that has only the job of
> assigning customer numbers, then, using the *before trigger, just
> replacing whatever number the incoming record has with the newly
> assigned number from your program?  That way there will never be a
> conflict to deal with, and a whole lot of field training that never
> needs to be done? (No need to teach the branches all of the rules for
> assigning customer numbers -  just tell all branches to always use 999
> as their new customer number.)
>
> --
> 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.