PrintPreviewCon trol navigate pages problem.

[Chris Dunaway]

I am using the PrintPreviewCon trol on a custom form to display a
report. The report is multiple pages. I have a NumericUpDown control
on the form to navigate the pages of the report. In the ValueChanged
event of the UpDown control I change the StartPage property like this:

private void udPageNo_ValueC hanged(object sender, EventArgs e)
{
ppReport.StartP age = Convert.ToInt32 (udPageNo.Value );
}

This works fine when *increasing* the page number, but it does not
work when paging down!

If I place a call to InvalidatePrevi ew just after I set the StartPage
property, then the page will change (going back down) but it causes
the preview to be regenerated. The preview is slow in generating so I
don't want to take this route.

Has anyone else experienced this issue? Is there a work around?

Thanks,

Chris

[Chris Dunaway]

On Mar 30, 9:11 am, "Chris Dunaway" <dunaw...@gmail .comwrote:

I am using the PrintPreviewCon trol on a custom form to display a
report. The report is multiple pages. I have a NumericUpDown control
on the form to navigate the pages of the report. In the ValueChanged
event of the UpDown control I change the StartPage property like this:

private void udPageNo_ValueC hanged(object sender, EventArgs e)
{
ppReport.StartP age = Convert.ToInt32 (udPageNo.Value );
}

This works fine when *increasing* the page number, but it does not
work when paging down!

If I place a call to InvalidatePrevi ew just after I set the StartPage
property, then the page will change (going back down) but it causes
the preview to be regenerated. The preview is slow in generating so I
don't want to take this route.

Has anyone else experienced this issue? Is there a work around?

Thanks,

Chris

For anyone else dealing with this same problem, the cause was a
boneheaded mistake by the developer (me). The StartPage property is 0
based. However, if you assign a page number beyond the number of
pages, it does not seem to throw an ArgumentOutOfRa nge exception. I
might have caught the problem sooner if I had gotten an exception.

Oh well,

Chris