Hi All,
Is there a system variable in PRO-IV to check to determine the printing row number in a report function? I need this variable for me to know when to issue a page break. Also, How do I use the 'page_break()' command? I tried it before but it seems its not working. Are there any restrictions in using this command? (it has no notes in the manual)
Thanks in advance for your advices!
Joseph
Click the link below to see the new game I'm developing!
Report row printing variable
Started by
Guest_Joseph V.G. Orendain_*
, Jan 28 2003 07:38 PM
7 replies to this topic
#2
Chris Mackenzie
-
- Members
-
- 372 posts
ProIV Guru
- Gender:Male
- Location:Bristol, United Kingdom
Posted 31 January 2003 - 08:28 AM
Although I was tempted to say RTFM, I won't because
I did and I couldn't see it! It's @LINE (shown on
the system variables screen) and available in logic.
I did and I couldn't see it! It's @LINE (shown on
the system variables screen) and available in logic.
The content and views expressed in this message are those
of the poster and do not represent those of any organisation.
of the poster and do not represent those of any organisation.
#3
Chris Mackenzie
-
- Members
-
- 372 posts
ProIV Guru
- Gender:Male
- Location:Bristol, United Kingdom
Posted 31 January 2003 - 08:30 AM
OK, so it is in the manual, doesn't work for
page-mode reports.
page-mode reports.
The content and views expressed in this message are those
of the poster and do not represent those of any organisation.
of the poster and do not represent those of any organisation.
#6
Chris Mackenzie
-
- Members
-
- 372 posts
ProIV Guru
- Gender:Male
- Location:Bristol, United Kingdom
Posted 03 February 2003 - 07:53 AM
Well if you want something that works write it yourself...
The content and views expressed in this message are those
of the poster and do not represent those of any organisation.
of the poster and do not represent those of any organisation.
#8
Gina Morfe
-
- Validating
-
- 10 posts
Member
- Gender:Female
- Location:Houston, TX United States
Posted 04 February 2003 - 08:49 PM
Hi Neg,
I somehow, have the same problem in here, bu I think I was able to resolved.
You can use your own line counting for the lines that the report printed (example: #LINE_COUNT +=1) and then on all groups, add the last key accessed in the control break, skipp after 99 (that will make it as a page break). then on the logic before process of CB, you can place your logic of:
Or you can use @LINE to determine your line. (But if you have a logical report within a report, @LINE is not a good counter. (Example if your @LINE in main report is 7, then you counted 5 more lines in the LR, when it returns to the main report, @LINE is still 7.
Basically, you will have to make combinations of page height, line counts, @line to satisfy your breaks.
I was able to pull one through here after days of UMSGs to count lines, and happily, it passed!
Hope this helps...
I somehow, have the same problem in here, bu I think I was able to resolved.
You can use your own line counting for the lines that the report printed (example: #LINE_COUNT +=1) and then on all groups, add the last key accessed in the control break, skipp after 99 (that will make it as a page break). then on the logic before process of CB, you can place your logic of:
IF #LINE_COUNT < 51 DSEL EXIT;
Or you can use @LINE to determine your line. (But if you have a logical report within a report, @LINE is not a good counter. (Example if your @LINE in main report is 7, then you counted 5 more lines in the LR, when it returns to the main report, @LINE is still 7.
Basically, you will have to make combinations of page height, line counts, @line to satisfy your breaks.
I was able to pull one through here after days of UMSGs to count lines, and happily, it passed!
Hope this helps...
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!
