Re: Statically binding multiple MAIN modules with display files

> Is there a good reason to bind together multiple application programs
> each with their own display files, or is the recommendation still to use
> dynamic CALLs?

I don't ever like to bind multiple modules together.  (Though I do the
same thing on Unix systems and it doesn't bother me there, not sure why...
probably because Unix systems always use "make" as the standard way to
build things)

If I'm going to have more than one module, I either use dynamic calls or
service programs, depending on how I want them to work.  Binding many
modules together makes for a messy complicated maintenance nightmare,
IMHO.

Though, I suppose if I had a very large program that wouldn't make sense
to break into service programs it might make sense to do it.

> What are the pros and cons of binding multiple programs together that
> have their own display files?  It seems to me that this is a place where
> the dynamic CALL still makes sense.

What I don't understand about this thread is this:  What difference does
it make if the modules have display files in them?  Is there some reason
that they are a special case?

Do display files have problems in this scenario?

Forgive my ignorance, but since I never bind modules together, I have no
experience with having display files in two bound modules.