Thanks Colin.

I was hoping one of you guys would respond to this. A few questions:

- 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?

- Do your suggestions also handle the line splitting problem which ocassionally occurs at the last line of one page to the first line of the next page? If not, what are your suggestions?

- Since this is not a "trivial problem" (no kidding!), are there docs to assist with Lisa's techniques? Sorry, but I couldn't make it to Frankfurt.

-Jeff


> >> I'm really suprised that there is no easy way to do this.
>
>Then you need to do some more thinking about it.
>
> >> HTML is an essential output format for VFP reports and this
>>> one little thing kinda blows it.
>
>Oh, I think that's a bit of an overstatement.
>
>At Frankfurt, Lisa described a couple of techniques that might be used to do this.
>
>1) Pull out the default XSLT used by HTMLListener to create the HTML and adjust it to produce output with no page breaks.
>
>2) Subclass and override the GetPageHeight() method of the listener to return a value that is sufficient to cover the entire report (essentially, one giant length page).
>
>You'll need to do some work in either case. This is not a trivial problem...
>
>- Colin