I think we need more specifics about the process and its timing before making a recommendation.
Wouldn't want to be clearing the file while records are coming in.
Maybe better to mark them.
Wouldn't want to process a record twice by accident. Might call for a flag field of some sort.
Or does the processing program simply delete records and it doesn't really get cleared with something like a CLRPFM or DELETE ALL.
Again, hard to say until we better understand the entire process at the 3000 foot level 😊
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 5
date: Tue, 11 Sep 2018 22:08:49 -0400
from: Buck Calabro <kc2hiz@xxxxxxxxx>
subject: Re: run a program when a file changes
On Tue, 11 Sep 2018 at 21:44, Booth Martin <booth@xxxxxxxxxxxx> wrote:
Several random times a day a file is cleared and then populated again
through DDM . When that happens I want to automatically run a program
that updates another file.
A trigger is on rows, so using a trigger would run the program for every
row - not a good solution.
It seems to me as if a trigger should work.
The program that would get called has all of the logic to process
records from file1 and put the right stuff into file2.
Put that same logic into a trigger, and when record 1 arrives, the
trigger fires, processing the row, sending the right stuff to file2,
etc.
That's simplistic, assuming the process doesn't need extensive
commitment control or anything like that.
--buck
As an Amazon Associate we earn from qualifying purchases.