I am control-breaking on a variable (which happens to be the first key of the primary file) in a paging report. I have a header before and after the records of the group. How would I prevent a page-break from happening in the middle of a group. In other words, start a new group on a new page if I know it will be broken up with a page break? Thanks.
Click the link below to see the new game I'm developing!
3 replies to this topic
#2
Lewis Mccabe
-
- Members
-
- 455 posts
ProIV Guru
- Gender:Male
- Location:Sarasota, Florida
Posted 21 July 2005 - 08:11 PM
You need to know when you encounter a record that it does or does not fit on a page. Once you begin the print you are committed. If you can determine it based on detail record count you can use GETLPSEQ. Many times we cannot determine the nature of data for print without doing a prepass of that data (read in an update prior to actual print). Can you give us more detail?
Lew
Lew
#3
Chris Pepper
-
- Members
-
- 369 posts
ProIV Guru
- Gender:Male
- Location:United Kingdom
Posted 21 July 2005 - 08:27 PM
If you think about it, you'll have to read the records twice, because you cannot start printing a group before you know how many records are in it.
Given that, it then depends on how volatile the dataset is. If the number of records will be changing during the report run then you'll need to extract the data you want to print to a temporary file (whether on disk or in memory depending on the size). This extract could actually build the headers and footers possibly, provided it was indexed so you could write the number of entries someone on the header record (once you've written the footer, or last detail record).
If the dataset is not volatile (or you are running on Oracle or something that will give you a static snapshot) you could make one pass to pproduce a temporary file (memory again?) that just had a record for each "header" value giving the count of entries. Then again if it's Oracle you could so some embedded SQL to count the number of lines in the group before processing it in ProIV - or nest in a Global Update that does a SEL-ONLY to count the number of records whenever you are about to start a new group (e.g. in Logic Next). I think a Global Update would be better than just doing an LSCALL in the same Function as ProIV might lose the position in the file... then again it might not - it sometime suprises me! Best to try this first as it would be more efficient than a Global Update!
Given that, it then depends on how volatile the dataset is. If the number of records will be changing during the report run then you'll need to extract the data you want to print to a temporary file (whether on disk or in memory depending on the size). This extract could actually build the headers and footers possibly, provided it was indexed so you could write the number of entries someone on the header record (once you've written the footer, or last detail record).
If the dataset is not volatile (or you are running on Oracle or something that will give you a static snapshot) you could make one pass to pproduce a temporary file (memory again?) that just had a record for each "header" value giving the count of entries. Then again if it's Oracle you could so some embedded SQL to count the number of lines in the group before processing it in ProIV - or nest in a Global Update that does a SEL-ONLY to count the number of records whenever you are about to start a new group (e.g. in Logic Next). I think a Global Update would be better than just doing an LSCALL in the same Function as ProIV might lose the position in the file... then again it might not - it sometime suprises me! Best to try this first as it would be more efficient than a Global Update!
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
