Difference in how declared variables handled in report breaks?

[Kenneth Brody]

On 11/6/2014 2:44 PM, Boaz Bezborodko wrote:
> On 11/6/2014 1:48 PM, Kenneth Brody wrote:
>> On 10/31/2014 3:19 PM, Boaz Bezborodko wrote:
>>> I was doing some processing where I wanted to collect the sum total of a
>>> number at a sub-total break.  When doing this with standard global variables
>>> such as aa(10,.0,g) it works fine.  Using the line aa=aa+{field}, at the
>>> break 'aa' is holding the correct value.  But when I tried it with a
>>> declared variable such as qty(10,.0,g) (using the line DECLARE qty(10,.0,g))
>>> the value is correct throughout the processing except that when it gets to
>>> the @wbrkn line the value goes blank.
>>>
>>> I'm assuming that this is normal behavior and that there is some brilliant
>>> reason why this should be happening so I'm curious as to what it is.
>>
>> What version of filePro are you using?  This sounds like a bug (item #497)
>> that was fixed way back in 5.0.06.
>>
> I'm using 5.06.00

Contact fpsupport and arrange to send them files to demonstrate.

-- 
Kenneth Brody