Colin,

It may not be a common problen now, but it will be when more people start using the ReportListener for HTML output.

I am well aware of the need for page breaks. I am also aware of the fact that the ReportListener does not handle them correctly for HTML output.

I have created seven different types of Management reports for a mission critical PeopleSoft migration project. The HTML reports are created automatically and emailed to Managaement throughout the day. The reports look great except for the page break issue of which Management immediately complained about.

They want it fixed yesterday and you are suggesting that I pour through all the VFP docs (which I have), all the source code, and write a paper on how to handle an issue which, in my opinion, is a bug in the first place?

Don't get me wrong. I think all the new reporting features for VFP9 are awesome and we want to use them extensively for MANY things.

However, this page break issue really bugs me because, well, it shoudn't be a complex issue.

When Management sees an issue like this, they say: "Fix it. Don't use VFP for HTML reports. Buy a third party product if you have to." And we don't want that, do we.

>Hi Jeff -
>
>Why are page breaks in the XSLT in the first place if this is a common problem? [..] Are there condition(s) where page breaks are absolutley required in the XSLT?
>
>I don't think this is a common problem. It may be a common request (I think you are the third that I've seen). But in many ways you are really asking why can't you drive to London from New York.
>
>Ask yourself your question again after you have considered the following:
>

• The VFP9 Report Writer generates page-oriented layout.

>
• The XML is a representation of the page-oriented layout

>
• Anything that is included in the product should produce acceptable results with any possible FRX that users may have developed.

>
• The VFP9 Report Writer allows page breaks on expressions, group footers, summarys, etc

>
>Do your suggestions also handle the line splitting problem which occasionally occurs at the last line of one page to the first line of the next page? If not, what are your suggestions?
>
>I have nothing to offer on this topic, sorry.
>
>Since this is not a "trivial problem" (no kidding!), are there docs to assist with Lisa's techniques?
>
>Apart from the source code to the _reportlistener.vcx in the FFC? And very comprehensive documentation? Take a look a the help file. I'd start with the ReportListener.GetPageHeight() method docs and work from there.
>
>But clearly there's an opportunity for an article on this topic, if you felt like writing one.
>
>- Colin