[EMAIL PROTECTED] wrote:
Page-Sequence optimization! Well I am not really sure how to do that. I have tried to reduce the number of tables and font specifications in table-cells. But if you could throw a pointer as to how I can achieve the page-sequence optimization, that'd be really helpful.
I would first try to imagine what you can logically break on. Since you are apparently doing some form of health insurance information, you can break on doctor or patient or geographical region perhaps. Find something your customer would like to see subtotals of, perhaps, and that can be a good place to start a new page sequence.
Next, after your fo:layout-master set, call a template that creates an fo:page-sequence for each of whatever that you are breaking on. I have yet to do this (my reports are much smaller), but this should work well for you.
[As an aside, I'm in the process of trying to move Oracle Reports-based reports to XSL at work. One thing I have upcoming is to build a stylesheet for a particular report that can dynamically break as above on *any* user-desired field: patient, doctor, hospital, state, etc., instead of being hardcoded to just break on one. So one customer gets his reports one-page-sequence per doctor, others one-page-sequence per patient, etc. I have no clue as to the difficulty of doing this, but you may wish to consider such a design yourself.]
Also, thankfully you didn't here, but just to warn you in case you may forget for a moment, be *very* careful not to accidently post any source XML data in any future question you have, as it appears that you are handling HIPAA data.
Glen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
