Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
HTML Output - How do I supress pagebreaks
Message
From
24/01/2005 06:06:03
 
 
To
22/01/2005 20:08:25
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Environment versions
Visual FoxPro:
VFP 9
Miscellaneous
Thread ID:
00979179
Message ID:
00979947
Views:
27
>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.

>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).
>


Hi Colin

Maybe essence of the problem lays in question, why would someone supress HTML pagebreaks at first place.

I would not mind HAVING page breaks provided that resulting HTML is accordingly previewed/printed afterwards when opened with IE.
But this is far away from reality.

Report that normally prints on 22 pages resulted in 47 (!) preview/print
pages when opened with IE. So my 'unsuspecting' page number expression showed naively page 22 on 47th page of the HTML printout.

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.

If this IS the case, then VFP team should consider coming up with something
simple, to at least supress HTML paging, since we cannot relay on it. Something like that 'PLAIN' option of report form command.

If I cannot GRANT paging to my users then I wld rather avoid it completely.

Your advice to Jeff is basically more correct way to implement 'patch' I adviced to Michael Collins (facing more less the same problem) in thread that Garret Fitzgerald is mentioning, since it does not requires changing original report.

But is still just suggested workaround not a real solution to - in my opionion as well, serious problem that everybody will face sooner or later with VFP9>HTML output option.

Best Regards
Sergio
*****************
Srdjan Djordjevic
Limassol, Cyprus

Free Reporting Framework for VFP9 ;
www.Report-Sculptor.Com
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform