Hector Valenzuela@CONTEXT
07/07/98 12:05 PM
I have a customer who is doing their invoices using BO.
Everything seems to work pretty good. However, here is the problem. In a simplistic approach. If you have 100 invoices, they get printed on company forms and each page has “page 1”. No problem. The problem arises when you have a customer with line items that goes beyond 1 page. So if you had one customer with three pages, we need to display page1, page 2, page 3 then the next customer page 1, page 1, etc… I’m printing the page on the global break header with all of the other Customer stuff (address,etc…). I’ve also tried the break header. Currently, they are using cursors and reading each line of the invoice to determine if there is more than one page but this is fairly cumbersome. Is there any other way to do paging in the way they want?
Thanks,
Hector Valenzuela
Context Integration
Listserv Archives (BOB member since 2002-06-25)
Hector,
Possibly… You have to have a SET number of rows that can appear on a page.
Say you have 20 rows on a page…
You need to have a runningcount for each of the customers invoices. You then have that Running Count divided by 20 (the number of rows that fits on a page). For the variable, you just truncate the decimal and show that value as the Page Number.
Thanks!
-rm
Listserv Archives (BOB member since 2002-06-25)
Hector Valenzuela@CONTEXT
07/08/98 08:58 PM
rm,
I had already tried that. It doesn’t work. The header doesn’t sense a change.
Thanks,
Hector
Hector,
Possibly… You have to have a SET number of rows that can appear on a page.
Say you have 20 rows on a page…
You need to have a runningcount for each of the customers invoices. You then have that Running Count divided by 20 (the number of rows that fits on a page). For the variable, you just truncate the decimal and show that value as the Page Number.
Thanks!
-rm
Listserv Archives (BOB member since 2002-06-25)
Hector,
A couple of weeks ago we struggled with the same problem. Unfortunately BO does not have a function RelativePage. One of the BO consultants came up with the next solution:
First of all you need to create a dimension-object in the report: Cust_Page = If ( <> “Dummy value”) Then Page() You need this object to make use of the RunningSum() function and to have a dimension in stead of a function which only has one instance (i.e. the page function). Make sure this object is type numeric.
After this you need to create a cell in your customer section which sets a page number to 1 when your customer section changes to a new cutomer:
Page()-(RunningSum(<Cust_page>;))+1 If you repeat this cell on every page (format cell, alignment), you create your own relative page number.
I hope this is of any help to you.
Best regards,
Susanne Bakker
ING Group The Netherlands.
Hector wrote:
I have a customer who is doing their invoices using BO. Here is the problem. If you have 100 invoices, they get printed on company forms and each page has “page 1”. The problem arises when you have a customer with line items that goes beyond 1 page. So if you had one customer with three pages, we need to display page1, page 2, page 3 then the next customer page 1, page 1, etc…
Listserv Archives (BOB member since 2002-06-25)