Hi:

Sorry I took so long to answer, been busy with hurricane Lenny in the local area.

I usually "select - join" everything I need for a report into a single cursor.
My customer was complaining because this took a lot of time b4 the report preview was available.
If I don't make the select and simply use filters and relations in the original tables, the report takes a long time to print but the preview appears as soon as a couple of records are available.

Thanks for the reply.


>>Hi:
>>
>> I have a report with a group band.
>> In the OnEntry of the group header I call a function that makes
>> some calculations on a public variable.
>>
>> In the last page I print this public variable.
>>
>> If the report has more than one page, the following happens:
>>
>> Looking at a page where a group starts I zoom/unzoom the report a couple of times.
>> Every time the zoom changes, VFP6 "reprints" the page, so the function
>> in the OnEntry of the group header is called again. When I jump
>> to the page where I print the variable that is calculated I find
>> is completely wrong since the function was called every time some
>> page where a group started was zoomed/unzoomed.
>>
>> Is this documented. Any workarounds?
>>
>>TIA
>>
>> BTW I can't use a "report variable" because the report is based in a "1 to many"
>> and I need this calculation for the parent records "only".
>
>Hola Raul,
>
>I do not know if this is documented, but I can understand why it happens.
>
>However, even for the most complex reports I try fo finish with a single cursor that has all the necesary information. In the case of a one to many relationship I don't care having the header replicated x number of times. This lets me use the report variables at will.
>
>José