Re: Data base triggers

["Nelson C. Smith" <ncsmith@xxxxxxxx>]

All except the first one.  I'm sure Booth meant to say *YES.

----- Original Message -----
From: "Jim Langston" <jlangston@conexfreight.com>
To: <RPG400-L@midrange.com>
Sent: Monday, January 24, 2000 9:09 PM
Subject: Re: Data base triggers


> Okay, now I'm confused.  Here are a number of replies:
>
> "Martin, Booth" <BoothM@goddard.edu> Wrote:
> Yes you can update the record with the trigger program itself.
> When you ADDPFTRG use:
> Allow Repeated Change  . . . . .   *NO
> and make the change to the buffer *BEFORE the *INSERT or *UPDATE.
>
> Scott Mildenberger <Smildenber@Washcorp.com> Wrote:
> This is possible, we have a lot of triggers that do at this.  You just
> change the field in the after buffer in your trigger program.  When you
add
> the trigger to the file, the trigger time must be *before and the
ALWREPCHG
> must be *yes.
>
> Hartman Richard <richard.hartman@brctsg.com> Wrote:
> We have triggers that default fields if they were not entered, which does
> not cause the trigger to fire again because the trigger is already editing
> the fields.
> The trigger only fires once per record when executed, so on the record
that
> was changed, anything the trigger does will only occur once after it is
> triggered.
>
> Which of these is "right"?  Or are they all?
>
> Regards,
>
> Jim Langston
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---