RE: Timestamp when a record is updated...

Tim,

You can if the access path is not shared and the trigger is written so 
that a recursive call error is not received.  If the access path is shared 
it will just receive an error.  This capability can be very powerful, but 
normally the update is triggered by an update to another file, IE: file a 
updates b which triggers an update in a.  If you cause a loop you will 
get an error at around 50 updates because the job stack will only 
support 256 entries.

David Morris.

>>> "Hatzenbeler, Tim" <thatzenbeler@clinitech.net> 08/19/99 05:06PM >>>
I have never written a trigger, but I do have a question concerning the
possibility of looping...
If you have a file with a trigger.  And you update the file, the trigger is
then activated, but if your trigger updates the same file, does it re-call
the trigger, and start a looping process....

thanks, tim

+---
| 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
+---