RE: Private storage, static storage, bound modules and service programs

 >> That's a pretty elegant concept, although it does mean I have to have an
activation group for every level of my stack.  But in the great scheme of
things, that doesn't seem to be all bad.

The biggest issue will be performance Joe.  AG creation while not the
overhead of job creation is still significant.  Of course if your design is
such that the AGs get created at the beginning of the day and never get torn
down until the user signs off - who cares.

I can't help wonder if there isn't a simpler answer though.  For example why
not have a single routine which is sensitive to the level of it's caller and
automatically stores the appropriate values in an array indexed by level?

Without knowing a bit more about what you are trying to achieve it is tough
to make a recommendation.

Jon Paris
Partner400
www.Partner400.com