Why am I losing value in global variable?

[John Esak]

That is my guess, one is really defined on the -v table.... But... And this
is admittedly really a stupid suggestion... But since it happened to me
once, I might as well mention it.  For a very long time one day, I struggled
to find out why a value derived from bom() was not working properly.  It
just was right sometimes and not others.  Very squirrelly and I was tearing
my hair out.  It turns out that elsewhere on this 800 table, years earlier I
had set bom as the alias for a lookup. :-(  Not the kind of thing that will
give a syntax error, although maybe it should... But it did conflate the two
values enough to make the one I was tracking incorrect.  Yes, I know there
is a billion to one chance that you've done something like this... But wall,
like I said, might as well offer it.

John 

> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Kenneth Brody
> Sent: Monday, August 31, 2009 11:51 PM
> To: Boaz Bezborodko
> Cc: filepro-list at lists.celestial.com
> Subject: Re: Why am I losing value in global variable?
> 
> Boaz Bezborodko wrote:
> > I have a report where I have the user input a date during selection 
> > processing.  That variable, 'bf', is established as a 
> global variable in 
> > the auto processing table.  I then make another variable, 'be'-also 
> > established in the auto processing table as a global 
> variable, equal to 
> > the beginning of the month of the first variable.  
> (be=BOM(bf) in the 
> > sort/select processing table) Both are listed on the 
> heading of a report.
> > 
> > The problem is that the report 'remembers' 'bf', but lists 'be' as 
> > blank.  When I go through debug 'be' is correct throughout 
> sort/select 
> > processing, but as soon as it hits auto processing prior to going 
> > through the report process 'be' becomes blank.
> > 
> > Why is a global variable being remembered when it is set through an 
> > INPUT command, but not otherwise?
> 
> Are you sure they are both defined in the automatic 
> processing table you are 
> using, and that they are both defined there with the ",g" flag?
> 
> -- 
> Kenneth Brody
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>