topic Re: PROC REPORT compute block adding an extra line, how to fix it? in SAS Procedures

PROC REPORT compute block adding an extra line, how to fix it?

A_Kh — Thu, 23 May 2024 13:29:33 GMT

Hello SAS Community,

Please anyone tell me why I'm getting an extra line of text when using compute before/after for 2 variables. Below is an example code.

Thank you!

data have;
input visit $ paramcd $ aval;
if find(paramcd, 'EQOL') gt 0 then gr=2;
else gr=1; 
cards;
Screen EQOL0101 2
Screen EQOL0102 4
Screen EQOL0103 3
Screen EQOL0104 1
Screen EQOL0105 2
Screen PGIS	2
Screen CGIS 3
Week4 EQOL0101 2
Week4 EQOL0102 4
Week4 EQOL0103 3
Week4 EQOL0104 1
Week4 EQOL0105 2
Week4 PGIS	1
Week4 CGIS 2
Week4 PGIC	1
Week4 CGIC 2
Week8 EQOL0101 2
Week8 EQOL0102 4
Week8 EQOL0103 3
Week8 EQOL0104 1
Week8 EQOL0105 2
Week8 PGIS	1
Week8 CGIS 2
Week8 PGIC	1
Week8 CGIC 2
;
run; 

proc report data=have;
	column visit gr paramcd aval;
	define visit/ order noprint;
	define gr/ order noprint;
	define paramcd/ 'Item' display;
	define aval/'Value' display;
	compute before visit/style={just=c};
		line @1 text $40.;
		length text $40;
		if visit='Screen' then text='Screening';
		else if visit='Week4' then text= 'Week 4';
		else if visit='Week8' then text='Week 8';
	endcomp;
	compute before gr;
		line @1 text $40.;
		length text $40;
		if gr=2 then text='EQ-5D-5L';
	endcomp; 
run;

Result:

Re: PROC REPORT compute block adding an extra line, how to fix it?

data_null__ — Thu, 23 May 2024 14:15:37 GMT

I think you may need this.

Sample 37763: Conditionally print a LINE statement in PROC REPORT

Re: PROC REPORT compute block adding an extra line, how to fix it?

Ksharp — Fri, 24 May 2024 01:48:51 GMT

You used TWO 'line' statement in two different computed blocks. Just combine these two computed blocks into ONE .


proc report data=have;
	column visit gr paramcd aval;
	define visit/ order noprint;
	define gr/ order noprint;
	define paramcd/ 'Item' display;
	define aval/'Value' display;
	compute before gr;
		line @1 text $40.;
		length text $40;

		if visit='Screen' then text='Screening';
		else if visit='Week4' then text= 'Week 4';
		else if visit='Week8' then text='Week 8';

		if gr=2 then text='EQ-5D-5L';
	endcomp; 
run;

Re: PROC REPORT compute block adding an extra line, how to fix it?

A_Kh — Fri, 24 May 2024 15:02:19 GMT

Hi @Ksharp ,
Thank you for the suggestion. Interesting, VISIT is also a grouping variable that is handled inside another grouping variable GR. This eliminated the unnecessary extra row. Could we also keep the original justification of text in the report? VISITs are centered, GR is left justified. I tried with ods escapechar style elements, it didn't help.

ods escapechar='~';
proc report data=have;
	column visit gr paramcd aval;
	define visit/ order noprint;
	define gr/ order noprint;
	define paramcd/ 'Item' display;
	define aval/'Value' display;
	compute before gr/style={just=c};
		line @1 text $40.;
		length text $40;

		if visit='Screen' then text='Screening';
		else if visit='Week4' then text= 'Week 4';
		else if visit='Week8' then text='Week 8';

		if gr=2 then text="~S={just=left} EQ-5D-5L";
	endcomp; 
run;

Re: PROC REPORT compute block adding an extra line, how to fix it?

Ksharp — Sat, 25 May 2024 07:08:20 GMT

Or you could try data _null_; suggest to use format $varying.




proc report data=have nowd;
	column visit gr paramcd aval;
	define visit/ order noprint;
	define gr/ order noprint;
	define paramcd/ 'Item' display;
	define aval/'Value' display;
	compute before visit/style={just=c};
		line @1 text $40.;
		length text $40;
		if visit='Screen' then text='Screening';
		else if visit='Week4' then text= 'Week 4';
		else if visit='Week8' then text='Week 8';
	endcomp;
	compute before gr;
		line @1 text $varying40. len;
		length text $ 40;
		len=0;
		if gr=2 then do;len=10;text='EQ-5D-5L';end;
	endcomp; 
run;

Re: PROC REPORT compute block adding an extra line, how to fix it?

A_Kh — Tue, 28 May 2024 13:21:42 GMT

Thank you @Ksharp for taking the time to look into the documentation and applying $varying format in my example.!

Very grateful to @data_null__ for the precious tips and guidance!

Appreciate your help, guys!