RE: ALDON Question

This to how Aldon works. Think about it like this: the program object in
your library already contains the module, so you don't need the module
object. 

You don't need to recompile all of the modules when recreating the *PGM
object. Remember, when Aldon recompiles, your production library is in the
recompile job's library list. Your development library is first, then QA
libraries, then any production libraries. Just change the modules you need
in your dev library, recompile them and the program. Unless you hardcoded
the module list when creating the program.... That's a no-no. Aldon's
designed to use the library list, so let it.

HTH,
Loyd

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Derham
Sent: Saturday, July 09, 2005 12:17 AM
To: MidRange List
Subject: ALDON Question

Have an application at a client site that consists of a program that 7 bound
modules. When the application was constructed in ALDON all seven Modules
were identified, along with a Binding Directory, supporting Display Files
and the bound program. Everything seems to work just fine but when I went to
check out the objects to make a change, I was surprised to find that the
program object was brought to my library as was the binding directory and
the source for all modules.     

What wasn't brought across were the module objects. 

 

My question: is this a normal ALDON characteristic or is this a function of
local settings that could be changed. It is a real pain to have to compile
all of the modules when you really only have to make a change in one.

 

Jack Derham

Direct Systems, Inc.