Procedures, Modules, Service Programs

["Birgitta Hauser" <Hauser@xxxxxxxxxxxxxxx>]

Hi guys,

 

I?m just curious and I?d like to know how to handle it:

Procedures, Modules, Service Programs and Programs

 

(We just had some discussions about it).

Currently I?m using several procedures within a single module (grouped
according functionality).

To make it easy I normally create a service program for each module
(exceptionally I also bind several modules with generic names for example
Date* into a service program).

Into a program only a single module gets bound and I never export procedures
from a program module.

 

An colleague argues having a lot of service programs is not good, he insists
in having a single service program with all modules for the whole
application, because there will be only a single activation.

I don?t like this idea, because: If I only want to use a string function for
my batch program all display and printer file and what else functions must
be activated.

 

I just like to know how you handle it and why.

 

Mit freundlichen Grüßen / Best regards

 

Birgitta Hauser

 

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)

"If you think education is expensive, try ignorance." (Derek Bok)

"What is worse than training your staff and losing them? Not training them
and keeping them!"