Hi Lisa, thanks again for your help.

I was referring to whether the Page x of y scenario had been sorted out.
I would consider this a bug or at best a 'glaring omission' .
I would assume that most users of Fox, would at some time or other use it to print forms, which will 90% of the time have a requirement to print Page x of y.

Other products do this very simply (e.g. Word)

And the fact that in the VFP report writer, it DOES know when to initialize the Page Number back to 1, it should also have a default facility to set the Page of back .

I know there are other considerations , and multiple passes have to be done, but I am surprised that this is not 'A Feature' shall we say , in VFP 9

These are just my comments , and again, I appreciate your help here.

Regards,

Gerard




>---
>Do you know if this issue has been resolved in VFP 9
>----
>
>Two answers, JIC, because the question isn't completely clear:
>
>1) The fact that you have to omit NOPAGEEJECT on the last report isn't an issue or a bug. It's a fact. You have to tell the engine what REPORT FORM command ends the concatenated job.
>
>2) The fact that you have to maintain group page totals separately from what the engine recognizes as total pages isn't an issue or a bug either, so it is not "resolved" in VFP 9.
>
>It has always been questionnable whether you could get a meaningful value from _PAGETOTAL, because there are a lot of user-settable parameters at work here, such as potential NORESET use, plus the fact that you can manually reset _PAGENO at any time that you feel like it in a UDF. It is a limited facility, but it works as designed.
>
>However you have some better facilities for handling the same requirement in VFP 9.
>
>HTH,
>
>>L<