Quantcast
Channel: Adobe Community : Popular Discussions - Reporting
Viewing all articles
Browse latest Browse all 38309

CFDOCUMENT - Retaining Look Versus Pagination

$
0
0
I have a problem with <CFDOCUMENT> paginating and honoring the formatting at the same time in both PDF and FlashPaper. I removed my <HTML> and <BODY> tags because I read somewhere that they mess up <CFDOCUMENT>.

If I run my report one person at a time, I can ignore pagination and the report looks fine. If the report runs to multiple pages, there is no predicting where the page will break, and there are no page numbers, but that’s fine.

However, when I put virtually the same code inside a<CFOUTPUT> (<CFDOCUMENT> is outside the<CFOUTPUT> because there is report data before that output) in order to run reports for multiple people, I start having problems.

Originally I attempted to use <cfdocumentitem type = "pagebreak"/> right before </CFOUTPUT> to get pagination, but the result was a blank page or two at the beginning and no page break between people. I have also unsuccessfully tried <p style="page-break-after:always;">.

My second option was to use <CFDOCUMENTSECTION> around the <CFOUTPUT> (I actually tried putting it in various places with no success.) I discovered that the pagination worked fine but I lost data formatting.

1. The font was changed to a larger size and possibly a different face.
2. Those rows that were formatted as:
<table>
<tr>
<table>
<tr>
<td>Question1</td>
<td>Answer1</td>
<td>Question2</td>
<td>Answer2</td>
</tr>
</table>
</tr>
</table>

were changed to an appearance of

<table>
<tr>
<table>
<tr>
<td>Question1</td>
<td>Answer1</td>
</tr>
<tr>
<td>Question2</td>
<td>Answer2</td>
</tr>
</table>
</tr>
</table>

There are some that were actually setup that way, and there were some set up with a single <TD>. Those tables with one or two <TD> elements remained that way, but the ones with four became two <TR> with two <TD>

3. An added factor is that the <TD> widths are table driven so as to be able to adjust how closely a question (first or third column) is followed by its answer (second or fourth column).

I have a problem with <CFDOCUMENT> paginating and honoring the formatting at the same time in both PDF and FlashPaper. I removed my <HTML> and <BODY> tags because I read somewhere that they mess up <CFDOCUMENT>.

If I run my report one person at a time, I can ignore pagination and the report looks fine. If the report runs to multiple pages, there is no predicting where the page will break, and there are no page numbers, but that’s fine.

However, when I put virtually the same code inside a<CFOUTPUT> (<CFDOCUMENT> is outside the<CFOUTPUT> because there is report data before that output) in order to run reports for multiple people, I start having problems.

Originally I attempted to use <cfdocumentitem type = "pagebreak"/> right before </CFOUTPUT> to get pagination, but the result was a blank page or two at the beginning and no page break between people. I have also unsuccessfully tried <p style="page-break-after:always;">.

My second option was to use <CFDOCUMENTSECTION> around the <CFOUTPUT> (I actually tried putting it in various places with no success.) I discovered that the pagination worked fine but I lost data formatting.

1. The font was changed to a larger size and possibly a different face.
2. Those rows that were formatted as:
<table>
<tr>
<table>
<tr>
<td>Question1</td>
<td>Answer1</td>
<td>Question2</td>
<td>Answer2</td>
</tr>
</table>
</tr>
</table>

were changed to an appearance of

<table>
<tr>
<table>
<tr>
<td>Question1</td>
<td>Answer1</td>
</tr>
<tr>
<td>Question2</td>
<td>Answer2</td>
</tr>
</table>
</tr>
</table>

There are some that were actually setup that way, and there were some set up with a single <TD>. Those tables with one or two <TD> elements remained that way, but the ones with four became two <TR> with two <TD>

3. An added factor is that the <TD> widths are table driven so as to be able to adjust how closely a question (first or third column) is followed by its answer (second or fourth column).

The bugs appear to be:
1. <cfdocumentitem type = "pagebreak"/> not working inside a <CFOUTPUT>.
2. <CFDOCUMENTSECTION> giving page breaks but also changing the font and various table elements of the report.

Viewing all articles
Browse latest Browse all 38309

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>