Re: The SAGA or is it Soap Opera Continues

Frank

That's cool.

Just a thought - when you said that the precompiler insisted on unique names across modules, might you have meant copy members? AFAIK, is should be possible to have the same names in separate modules that are linked into one program. I certainly hope so, as I have a need for separate modules to handle things like case sensitive vs. case insensitivity. You cannot set sort sequence on the fly, has to be done at compile time, so I need separate modules for each.

Again, each module contains code only for itself and knows nothing about another module. Hence, no conflict. Now copy members - well - you might look at using /include instead of /copy and see what happens. Look them up first and see what they do differently.

HTH
Vern

frank kolmann wrote:

Thanks Vern

The code I have is a bit big.
I will set up a small example to show the problem and post it.
I will need to set up a DDS PF and the code will do some SELECTs and
some UPDATES. Seems weird saying this but I hope the precompile fails.
Sometimes the precompiler accepts the non unique host variables.
This may take me a day or so.

PS. Thanks to everyone for the help. If nothing else I now have a better
perspective on the issue.

Regards
Frank

From: Vern Hamberg <vhamberg@xxxxxxxxxxx>

Now, to the precompiler - how can it insist on unique names across modules

- it

creates only one module at a time, right? It can know nothing about other
modules. We need to hear how to duplicate the problem. Give us a short

source
>member and how you compile it, please.

The matter of local variables not usable as host variables - I'm not sure

that's

the case. It MIGHT be that you can't use a local variable of the same name

as a

global for a host variable. But it's been at least a week since declaring a

host
>variable, so I forget!!!

HTH
Vern