Re: Record was Change

[rob@xxxxxxxxx]

Scott, 
What he is saying is to check the old/new buffer and see if they differ at 
all.  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.

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





Scott Mildenberger <scottmildenberger@xxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
07/25/2003 08:21 AM
Please respond to RPG programming on the AS400 / iSeries
 
        To:     RPG programming on the AS400 / iSeries 
<rpg400-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: Record was Change


That is why it is a good idea to use a trigger to update the
"job stamp" info, then it is consistently updated regardless of
what other programs do.

Scott Mildenberger
--- keith_mccully@xxxxxxxxxxxxxxx wrote:
> 
> I've used file "job stamps" a lot and normally find them very
> useful. Just
> one caveat: make sure that there is control over usage and
> updates. For
> example, I've seen too many "edit record" programs that update
> the "job
> stamp" change details regardless of whether anything has
> actually been
> changed (confirm = No)!
> 



__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
_______________________________________________
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.