Journaling the file would have supplied this information for you and I think
the effort would have been far less and the results more certain.
For this kind of use I can't see how anything can beat using the journals
and since it's been around since the system 38 only a few hold out sites
would not be able to use this technique...
Triggers have their place but in this case I don't think it's a good fit.
But so long as you have what you need, that's the main thing. I've been
known to take the long way round to get a different perspective :)
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Nick_Radich@xxxxxxxxxxxxxx
Sent: Wednesday, 27 February 2008 5:12 a.m.
To: Midrange Systems Technical Discussion
Subject: RE: Journaling
Thanx Rob,
I just finished writing my Trigger Pgm.
I am only using it on one file for a 1 time shot type of thing. I want to
see where some fields are getting updated from.
Thanx,
Nick
Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516
nick_radich@xxxxxxxxxxxxxx
rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/26/2008 08:24 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: Journaling
The easiest way is to journal. Not only is it the easiest way, but it
will stand up in an audit. The use of a trigger to record before/after
images to a history file can easily be thwarted by modifying the history
file. You mess with a journal receiver and the gap will definitely be
noticeable.
That being said, triggers are cool and I have some easy samples that can
quickly be modified to your use.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.