Pagenumber and Problems ....
I want to accomplish the following:
Within an app the user can print multiple contracts (by multiselect), each contract can have multiple pages.
* I want each contract numbered from 1 to the number of pages this particular contract has (not the number of total pages of the print job.)
If I set the dataset of the Report-Page to Contract then i can use
<page>: Delivers the correct numbering within a contract.
<totalpages>: unkown number ??? value is decremented after each contract.
<totalpages#>: number of pages of the print job
<page#>: Number of page within the printjob.
also <totalpages> is only filled if two-path is activated.
Questions:
Is there a bug in the evaluation of <totalpages>, because its count back?
-> I thought it would be the count of pages produced within the linked page-dataset (which i need).
Is it possible to calculate this var also within a single-path report.
Finally: If i link the dataset to the report (outside),
<totalpages> is always the number of the printjob.
<page> is always the page-number within the printjob.
Bug or feature?
thx
Dave.
Within an app the user can print multiple contracts (by multiselect), each contract can have multiple pages.
* I want each contract numbered from 1 to the number of pages this particular contract has (not the number of total pages of the print job.)
If I set the dataset of the Report-Page to Contract then i can use
<page>: Delivers the correct numbering within a contract.
<totalpages>: unkown number ??? value is decremented after each contract.
<totalpages#>: number of pages of the print job
<page#>: Number of page within the printjob.
also <totalpages> is only filled if two-path is activated.
Questions:
Is there a bug in the evaluation of <totalpages>, because its count back?
-> I thought it would be the count of pages produced within the linked page-dataset (which i need).
Is it possible to calculate this var also within a single-path report.
Finally: If i link the dataset to the report (outside),
<totalpages> is always the number of the printjob.
<page> is always the page-number within the printjob.
Bug or feature?
thx
Dave.