Re: Record was Change

Isn't it nice when IBM thinks of everything and saves you the hassle of 
checking old/new buffer?  Thanks for the tip.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





Douglas Handy <dhandy1@xxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
07/25/2003 11:28 AM
Please respond to RPG programming on the AS400 / iSeries
 
        To:     RPG programming on the AS400 / iSeries 
<rpg400-l@xxxxxxxxxxxx>
        cc:     RPG programming on the AS400 / iSeries 
<rpg400-l@xxxxxxxxxxxx>
        Fax to: 
        Subject:        Re: Record was Change


Rob,

> A lot of times an edit program does an UPDATE when actually no 
>update was really performed.  Thus you've lost your old history if you 
>update the timestamp.

I like to set these fields via a trigger with ALWREPCHG(*YES) and
TRGUPDCND(*CHANGE).  In this case the trigger only fires when the buffer 
has
actually changed, so even if the edit program performs an UPDATE operation 
the
old data is not affected.

And triggers set the contents regardless of the method used to update the
file...

Doug
_______________________________________________
This is the RPG programming on the AS400 / iSeries (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.