Thanks Tom,
Once again I stand corrected. This works for footer sections, not header
sections.
Given the original problem, I am not sure why it would not display. A
summary variable would still display but it would give a null or zero amount
for the first break and probably display the summary of the first break at the
top of the second break and so on. If it is a summary variable then you might
be able to get it in a header section by creating a stored procedure to calculate
it and then call it with a variable in the HEADER section.
The question back to Bill is: What is the purpose of the variable? Is it a
summary variable? A lookup to another table? Also, as Tom asked, why are
there 2 break points on the same column?
Best regards,
Mike Young
On Sat, 12 May 2001 09:56:13 +1000, Tom Grimshaw wrote:
>G'day Mike,
>
>At 15:33 11/05/01 -0700, you wrote:
>>Hi Bill,
>>
>>This is caused because the variable is not evaluated until the DETAIL
section
>>is hit. Set the variable to be in the DETAIL section and then go ahead and
>>locate it physically in the HEADER section. It should print fine after that.
>
>I think not. As the variable will not be defined until the detail section
>the first header will show no value for the variable, the second header
>will show the value for the first detail section.
>
>What I would do is to set the section for the var to be the header and
>position it in that section.
>
>Warmest regards,
>
>
>Tom Grimshaw
>coy: Just For You Software
>tel: 61 (0)2 9552 3311
>fax: 61 (0)2 9566 2164
>email: [EMAIL PROTECTED]
>mobile: 0414 675 903
>street: 3/66 Wentworth Park Rd Glebe NSW 2037
>post: PO Box 470 Glebe NSW 2037 Australia
>temp web site: 210.9.46.35
>
> _/_/_/_/_/_/_/_/ _/_/_/_/_/_/ _/ _/ _/_/_/_/_/
> _/ _/ _/ _/ _/
> _/ _/ _/ _/ _/
> _/ _/_/_/_/ _/ _/_/_/_/_/
> _/ _/ _/ _/
>_/ _/ _/ _/ _/
> _/ _/ _/ _/_/_/_/_/
>
