RE: Log file of file changes

My apologies for not reading closely. Yes the journals are intended to do what you are looking for. The journal receivers are your log files.

All you need to do is read through them. You only need to interrogate them in order to create a transaction file of your own device.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Wednesday, October 30, 2013 12:46 PM
To: Midrange Systems Technical Discussion
Subject: RE: Log file of file changes

I HIGHLY recommend the use of a trigger program in this instance.
We use this process for NUMEROUS files - and it has proven to be a godsend

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Wednesday, October 30, 2013 3:44 PM
To: Midrange Systems Technical Discussion
Subject: Log file of file changes

All,

We had an issue recently about how a couple of prices got changed. The salesrep (who has _some_ control over pricing) says he didn't do it, and no one in the office remembers doing it. In fact, it was the sales rep who brought it up wanting to know what the %#@* is going on? :) By looking at month end backups, I know it happened sometime in August. Nothing like bringing it to our attention on a timely basis, right?

Anyway, in discussing it, the buying VP suggested a log file of changes. I think it's a great idea and it seems to me to be an ideal use for a trigger. Whenever a record is added/updated/deleted, just have the trigger write the record to this log file. It can have the same record layout as the file in question, plus add a few fields such as user and timestamp.
Seem reasonable? I've never written a trigger before but I can figure it out.

The file is currently journaled, but that's not really what journaling is for, IMO.

Thanks for any ideas.

--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my company. Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.