Re: a need for speed

Rob et al,

> Or instead of modifying the program(s) that maintain the detail file, put
> a trigger on the detail file to maintain the summary.

Having a trigger (or modifying the other programs which modify the
detail file) may be the optimum solution if all that occurs are record
inserts.  But what should a delete trigger do when if finds the detail
record being deleted happens to match a current value in the summary
file?  You don't know what new value to place in the summary file
(assuming the detail file is unordered and there is no relevant LF
access path).

A record update of one of the relevant fields could also if the fields
values in the "was" buffer match a summary record instance.

However, if only record insertions occur, then my vote is for a
trigger on the detail files which either directly maintains the
summary file or puts entries to a DTAQ to defer that task to another
job.

Doug