Why am I losing value in global variable?

[Boaz Bezborodko]

Kenneth Brody wrote:
> 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?
>
That was it.  This was my Auto-processing line: be(8,mdy/) ; bf(8,mdy/)

I had this working fine when both variables were INPUTed in another 
table and they appeared on the report.  I hadn't realized that an INPUT 
made the variable global.   I also thought that putting the variable in 
auto processing made it automatic.

Thanks for the assistance.

Boaz