Re: a need for speed

[Douglas Handy <dhandy@xxxxxxxxx>]

Richard,

> one modification (delete, insert,  change) for partial key A, B, C then run
> a little PGm that will partial manage the summary file (delete for key and
> rebuil for this key)

But therein lies the rub -- you need a quick way to rebuild for the
key so we are back to the "need for speed" unless, as I mentioned
previously, the detail file is ordered or has a LF which can be used. 
*If* the LF exists or can be builtt, or if record deletions or updates
"never" occur to this file, then the trigger seems like a great way to
keep the summary file updated.

A rsummary rebuild program should stil be created for the first time
population of the summary and as a contingency for when the inevitable
delete which "never" occurs really does happen.  A delete or update
trigger could even set a flag somewhere that allows the report to
detect a rebuild of the summary file is required.

Doug