RE: Record was Change

Do the updation of the time stamp with a trigger. If before and after are
the same its not a real update, But do this in a triggered program and never
worry again about it. 
 
 
 
---------------------------------------------------------
Booth Martin http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: Saturday, July 26, 2003 2:52:47 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Record was Change
 
I mean Code Generation Tools (ie. CASE Tools) Like SYNON, LANSA etc....
I hope, If the program is hand-coded, that issue(Updation of Job stamp
without Real Update) Could be eliminated easily.
 
Murugesh
 
-----Original Message-----
From: keith_mccully@xxxxxxxxxxxxxxx
[mailto:keith_mccully@xxxxxxxxxxxxxxx]
Sent: Friday, July 25, 2003 8:09 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Record was Change
 
 
 
Not sure what TOOLS is? But,unfortunately, the programs that I was
referring to were straightforward, hand coded RPG.
 
Scott's trigger suggestion is good because it enforces consistency across
file usage.
 
Keith
 
 
 
>Hope keith is talking about Programs generated by TOOLS..Am i right Keith?
 
>Murugesh.
 
-----Original Message-----
From: keith_mccully@xxxxxxxxxxxxxxx
[mailto:keith_mccully@xxxxxxxxxxxxxxx]
Sent: Friday, July 25, 2003 2:24 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Record was Change
 
 
 
>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)!