DATA Step, Macro, Functions and more

First row of Proc report table is getting cuttoff

Reply
Contributor
Posts: 37

First row of Proc report table is getting cuttoff

Any idea as to why my first row is getting cuttoff?

Attachment
Super User
Posts: 23,262

Re: First row of Proc report table is getting cuttoff

Posted in reply to nirali514

Please embed the image into your post using the photo option. Many uses will not download a zip file. 

Contributor
Posts: 37

Re: First row of Proc report table is getting cuttoff

Thank you for the idea, please see the picture below!

 

spacing.JPG

Super User
Posts: 13,304

Re: First row of Proc report table is getting cuttoff

Posted in reply to nirali514

Is that image from an Excel document by chance? I've seen such things when a row height is too short for the displayed text size.

If so something may have accidentally changed the row height or some instruction in the proc report code may be doing something to the height.

 

Can you share the code used to generate that table?

SAS Super FREQ
Posts: 9,320

Re: First row of Proc report table is getting cuttoff

Hi: Another possibility is that is a screen shot of a PDF output. In PDF if you are at anything smaller than 100% in Acrobat Reader, your row heights and lines can sometimes look wonky.

It would really help to have ALL the code to see what destination was involved.

cynthia
Contributor
Posts: 37

Re: First row of Proc report table is getting cuttoff

Posted in reply to Cynthia_sas

Hi Cynthia,

 

Here is all of my code:

 

title1 font = 'Times New Roman' height = 12pt justify = center underlin = 0 color = blue bcolor = white 'Attachment I';

title2 font = 'Times New Roman' height = 12pt justify = center underlin = 0 color = black bcolor = white 'Response'

 

proc report data = attach1 nowindows headline headskip missing center

style(report)=[cellspacing=2 borderwidth=2 bordercolor=black]

style(header) = {font_weight = light font_face = 'Times New Roman' font_size = 8pt just = center cellheight=.22in }

style(column) = {font_face = 'Times New Roman' font_size = 8pt just = center /*asis = on*/ cellheight=.15in};

column

('^S={borderleftcolor=black borderleftwidth=3} '('^S={borderrightcolor=black borderrightwidth=3 borderleftcolor=black borderleftwidth=3 borderbottomcolor=black borderbottomwidth=3}Sample' case ))

('^S={borderleftcolor=black borderleftwidth=3 borderrightcolor=black borderrightwidth=3 borderbottomcolor=black borderbottomwidth=3}Response'

 

 

('^S={borderleftcolor=black borderleftwidth=3 borderbottomcolor=black borderbottomwidth=3}Panel 1' resp1)

 

 

('^S={borderbottomcolor=black borderbottomwidth=3}Panel 2' resp2)

 

 

('^S={borderbottomcolor=black borderbottomwidth=3}Panel 3' resp3) )

('^S={borderleftcolor=black borderleftwidth=3} '('^S={borderleftcolor=black borderleftwidth=3 borderbottomcolor=black borderbottomwidth=3}Mean' mean )) ('^S={borderrightcolor=black borderrightwidth=3} '('^S={borderrightcolor=black borderrightwidth=3 borderbottomcolor=black borderbottomwidth=3}%CV' cv )) ;

define case / display ' ' center style=[cellwidth=16mm] ;

define resp1 / display ' ' center style=[cellwidth=16mm];

define resp2 / display ' ' center style=[cellwidth=16mm];

define resp3 / display ' ' center style=[cellwidth=16mm] flow ;

define mean / display format = 12.1 ' ' center style=[cellwidth=16mm];

define cv / display format = percent8.1 ' ' center style=[cellwidth=16mm] ;

compute case;

if case <1000 then call define(_col_,"style","style={borderrightcolor=black borderrightwidth=3 borderleftcolor=black borderleftwidth=3}");

endcomp;

compute mean;

if mean <5000000 then call define(_col_,"style","style={borderleftcolor=black borderleftwidth=3}");

endcomp;

compute cv;

if cv <5000000 then call define(_col_,"style","style={borderrightcolor=black borderrightwidth=3}");

endcomp;

run;

 

SAS Super FREQ
Posts: 9,320

Re: First row of Proc report table is getting cuttoff

Posted in reply to nirali514
HI, this is NOT all your code. You do not show the ODS statements or the style that you're starting with. Without an ODS statement, we can't see what destination you are trying to use and without data, then someone has to read your mind and make fake data with the same variables and same values that you have in order to test any code. And the code that you've posted does not correspond to the output you showed in your screen shot. Without STYLE overrides, I only see a column statement that has these variables:
column case resp1 resp2 resp3 mean cv;

That is 5 items on the report row. And yet, in your screen shot, you show only 4 items #, x, y and z.

In addition, the FLOW option that you specify for RESP3 does not make sense, given that FLOW is a LISTING only option that is ignored by ODS destinations. The code you've posted does not seem to match the output you've posted.

So I do not see how the code you've posted generates the screen shot you posted that has variables named x, y and z, especially since you have different column headers in the code you've posted.

cynthia
Ask a Question
Discussion stats
  • 6 replies
  • 90 views
  • 0 likes
  • 4 in conversation