Hi Lisa.

I misunderstood.. when you mentioned about a VFP9 solution, I took it that you meant 'in general' there was a solution to this Paging problem, rather than the specific query regarding the Navigation buttons.


It seems there is a lot in VFP9 to do with reporting..

Regards,
Gerard

>--
>I am not clear on this.
>If you issuse a NoPageEject and Preview a no. of reports (with NoPageEject excluded from the last one), do you still get the Navigation up and Down icons for 'All' the reports , so that you can view the 'Full' print job all at once.
>Is this tru for VFP8 and VFP9 ?
>---
>
>Gerard,
>
>I specifically said this was a VFP 9 solution, or thought I did.
>
>Preview and rendering of previews is completely different in VFP 9 object-assisted reporting mode; you're not seeing this because you need to play with it to see it <s>. That's why you're not clear on it.
>
>As far as "still" getting the navigation arrows... the point in general is that the user will be UNAWARE that the reports were separate commands. It is all print job and will appear as a set of pages, from the user's point of view.
>
>The user should neither know nor care how many REPORT FORM commands there are, any more than the user should know or care how many INSERTS it took you to create a set of child records for an order <s>.
>
>But wait, there's more.
>
>As far as "still" getting the navigation buttons... you should also realize that they are different buttons, and they are under your control.
>
>ReportPreview is a VFP app.
>
>So potentially if you *want* to you could maintain a set of page pointers to the initial pages of each REPORT FORM command, and tell Preview about this collection. You could add a button to the toolbar that said "skip to first/last page of each set" much like "skip to the beginning/end of the chapter".
>
>As a result, potentially, the user *could* be aware of the separation between your "report segments" ... *if* you decided that wanted to make them aware of it.
>
>Cool idea, and pretty darned easy to implement, leveraging the same few lines of code it would take to create a reset page total.
>
>Yes, it's not native. And, yes, in order to have this type of functionality available to us we need to juggle multiple pagination systems. <s>
>
>>L<