CALLed table erase DECLARE EXTERN values after lookup

[Kenneth Brody]

Quoting Tyler (Thu, 4 May 2006 14:47:54 -0700):

> Well, this is a nasty one.  I think it must be a bug.
>
> I DECLARE GLOBAL in one processing table (temp), which then calls
> another with a DECLARE EXTERN(temp2).
>
> The DECLARED value in CALLed table temp2 is just fine until the line I
> do a lookup.  The value of all DECLARED EXTERN variables are then
> blanked.  Can anyone explain why this should be?  I'm using v5.0.14r4
> on SCO.
[...]
> Below are the relevant processing tables.  The values for all DECLAREds
> disappear after the first lookup in the CALLed table, right after the
> debug on statement.  Can anyone tell me why it does this?
[...]
> :ccCustNum ne "":lookup ccfile  k=(ccCustNum&ccCardNum)    i=B -nx:
[...]

Is this a lookup to the main file?  (ie: are you sitting in "ccfile"?)

This has already been fixed post-5.0.14:

(All) #783

    A non-dash lookup to the main file may clear non-",g" DECLAREd
    variables.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com