modules, service programs, etc. (i hate it when i forget to switch to plaintext)!!!!

[rick.baird@xxxxxxxxxxxxxxx]

sorry bout the last raw html post.

I'm creating a rather large file maintenance program, split up into several
modules.  Each of the modules perform specific portions of the maintenance,
and they also call other functions out of other service programs.  they all
have 'nomain' specified, and they will be bound to a driver program that
will call each one.

I can see a future where the individual modules in my program might be
called by themselves from other programs, so i thought it might be nice to
wrap them up into a service program for easy access.
what I'm looking for is a little advice on how you all would design such a
thing.

should I eschew the original model of creating a program of mutliple
modules, and just create a driver program that calls the modules from a
service program?

or should i go ahead and bind them together with the driver and if i decide
to use one of these modules in another program, just bind that the module
with the program?

or some combination of both?

clear as mud?

thanks,

rick