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

Not sure it would be that simple in real life however...

I'd be willing to bet a (cheap) lunch that the program creating the
record in the customer file creates records in other files or calls
other programs that create records using the same user inputted
customer number...

You'd have to track down all those other files, and put a trigger on
all of them.

I'd probably build one trigger that handle every file, and have it log
in a new table the original and new number when it generates it during
the add to the customer file. The log table could then be used when
records are added to the other files.

Charles

On Thu, Sep 1, 2011 at 2:04 PM, Rory Hewitt <rory.hewitt@xxxxxxxxx> wrote:

Booth,

That's a *great* idea.

Rory

On Thu, Sep 1, 2011 at 9:59 AM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

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.