--
During HTML extraction, VFP9 progress bar correctly reported extraction of 22 pages! So where is the problem? Is it BROWSER or is it HTML itself ?

I beleve that VFP9 report engine reported correctly 22 pages in this case, and that is IE preview/print engine - where the problem lays.
--

It's actually a combination of things, including the header and footer area that IE imposes on the layout, which the original report page size is not adjusted for, as well as the difference between whole and printable page in the original report. Also, remember that your users on the client side have different printers than the report was originally generated for and these printers may have different "unprintable areas". This is something that nobody can control when designing pages to be printed from a browser. Ordinarily people who want total page layout control and also want printing from a browser provide a second, "printable" view for this purpose, such as the JPGs mentioned below.

Meanwhile... as far as being able to "grant" your users printing ability... there are several options for creating unpaged output. I have addressed some of them briefly in another thread. You can create completely unpaged output with no headers and footers (but it will never be perfect) or you can create an XSLT that delivers a second, perfectly printable but plainer, view that you attach with a link to each page header.

As another option, HTML being HTML, you might think of a completely different way of creating paged html output that does print properly. Specifically, page at a time. It is pretty easy to do this, with a TOC approach. I showed this at DevCon with generated output in frames that shows the page numbers on the left and provides JPGS, perfect page renderings, for each page on the right, and also with generated output showing page numbers on one side but single-paged html output on the other.

You can also provide the output page-at-a-time from the server, which basically is like the "next X # of records" that people like to get in their browser rather than getting all 1000 pages of the report at once.

When you use the RANGE option to get single-paged output from the default HTML/XSLT, whether in a frame with multiple files or generating separate pages from the server on demand, the single pages will print pretty darned well, allowing for that IE header and footer item and the printer-variation issues that we mentioned above.

HTH,

>L<