topic Re: Supress page break after table in ODS and Base Reporting

Supress page break after table

Matyas — Tue, 24 Jul 2018 15:00:47 GMT

Hi,
I would like to know if there is a way how to supress last page break in proc report so I can use ods rtf text to put text immediately after the table and not on the other page.

Example code:

proc report data=data_table nowd split="~" out=pom;
		columns page p ord param value value0 value1;
	
		define page/order noprint;
		define p/order noprint;
		define ord/order noprint;

		define param/display style(header)=[just=l] style(column)=[asis=on indent=0 cellwidth=8.6cm ] " ";
		define value/display style(header)=[just=c] style(column)=[indent=0 cellwidth=4.47cm just=c] "Total~N=XXX";
		define value0/display style(header)=[just=c] style(column)=[indent=0 cellwidth=4.47cm just=c] "Group1~N=XXX";
		define value1/display style(header)=[just=c] style(column)=[indent=0 cellwidth=4.47cm just=c] "Group2~N=XXX";	

	    compute before p / style={cellheight=0.26cm FONTSIZE=1mm};
			line ' ';
	    endcomp;

		break after page / page;
	run;

ods rtf text="#S={outputwidth=100% just=l} {Region: Overall}"

Thank you for any suggestions..

Re: Supress page break after table

Cynthia_sas — Tue, 24 Jul 2018 19:40:20 GMT

Hi:
Have you tried using STARTPAGE=NO on the ODS RTF statement?
Cynthia

Re: Supress page break after table

Matyas — Thu, 26 Jul 2018 10:41:51 GMT

Thank you Cynthia, that works if I wont use

break after page / page;

because now the break statement doesnt start new page. I want to be able to break table after lets say it gets 13cm height, and still I want be able to add some text below table on last page with ods rtf text statement

Re: Supress page break after table

Cynthia_sas — Thu, 26 Jul 2018 12:49:52 GMT

Hi:
I'm sorry, I don't understand what you mean when you say you "want to break table after .. it gets 13cm height" -- how does your "page" variable cause a break every 13 CM or 5+ IN? Or, do you just want approx 13 CM between the very last table and the ODS RTF TEXT?

Since there's no data to test with, it's very hard to visualize what it is you're currently getting and what it is you want. And since you have 3 ORDER variables, all as NOPRINT, it's nearly impossible to make fake data that would work with your program.

Cynthia