RE: RE: Activation Group Issues ?

Greg,

>Anyhow, the program is down to a barely acceptible 2 hours 20 minutes
>now, whereas it would have run well over 24 with all those file
openings
>and closings, so I feel better, though I can't help thinking the
>performance could be tweaked further.  It used to run in a half an hour
>before we added these new fields.

As far as further performance benefits go, if this is a 'control' type
of file, you might consider reading all the records into an array
(defined in the procedure using the STATIC keyword) the first time the
procedure is called, and then reading data from the array (using the
same key) on each subsequent call, thus removing the file I/O for most
procedure calls. I've used that technique to drastically reduce
subprocedure call time and increase performance.

Of course, if the file is very large, this might not make sense. And the
procedure would need to be in a service program that uses a named
activation group, so the service program (and the array itself) remain
in memory between calls.

Just a thought.

Rory