:-( ).
That's probably because the export to PDF functionality prints on a "per
view" basis, that is, if there is a page break on the current view, it will
still print one page for the entire current view.
I do not know of many workarounds. If you want total flexibility for
printing to PDF, including the amount of pages printed in one PDF document,
you will have to use a third-party component to print your forms to PDF. But
this will be alot of work to code, not to mention more work if you want your
forms to appear exactly as they do in InfoPath.
---
S.Y.M. Wong-A-Ton
> Hi,
> Just getting to the end of a big enterprise deployment of InfoPath and the
[quoted text clipped - 9 lines]
> TIA for any help.
> Thanks.
jpr - 12 Aug 2007 12:34 GMT
I was afraid of that. How hard would it have been to do page breaks? :-(.
It's interesting, the developer docs on the fixed format output
(http://msdn2.microsoft.com/en-us/library/aa338206.aspx) talk about all of
the special cases in it for doing page breaks with InfoPath.
Thanks.
-jpr
> That's probably because the export to PDF functionality prints on a "per
> view" basis, that is, if there is a page break on the current view, it will
[quoted text clipped - 21 lines]
> > TIA for any help.
> > Thanks.
S.Y.M. Wong-A-Ton - 17 Aug 2007 02:08 GMT
I know... but I suspect it was probably more due to time constraints rather
than it being hard to do. Thanks for the link, BTW.
---
S.Y.M. Wong-A-Ton
> I was afraid of that. How hard would it have been to do page breaks? :-(.
>
[quoted text clipped - 30 lines]
> > > TIA for any help.
> > > Thanks.