cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
gzr2mz39
‎08-23-2020
  • 217 Posts
  • 5 Likes Given
  • 1 Solutions
  • 3 Likes Received

forward slash (/)

by Jade | Level 19 in Graphics Programming
‎08-29-2011 02:48 PM
2 Likes
‎08-29-2011 02:48 PM
2 Likes
Look in the PROC REPORT documentation at the SPLIT= option.  Notice the default.  Then think about your define statement. ... View more

tagattr='format:###%' doesn't show 0%

by SAS Employee in Graphics Programming
‎08-29-2011 02:07 PM
‎08-29-2011 02:07 PM
A format of ##0% may work.   But the easiest way to get percentages is to format them as percentages in SAS as percent so that they come out the way you want. (eg. 10%) The tagset automatically detects percentage values and does the right thing with them. Eric ... View more

proc report compute block percent format

by Jade | Level 19 in ODS and Base Reporting
‎08-24-2011 03:42 PM
‎08-24-2011 03:42 PM
Increase the width of the format you need to consider that negative values are printed with parenthesis.   You may also want to consider the PERCENTNw.d ... View more

ods pdf: 3 footnotes on the same line

by Diamond | Level 26 in ODS and Base Reporting
‎08-23-2011 01:21 AM
1 Like
‎08-23-2011 01:21 AM
1 Like
Hi,   You can put 3 text strings into 1 footnote: Footnote j=l 'left' j=c 'center' j=r 'right'; And most destinations will put the 3 strings on 1 footnote line. Cynthia ... View more

ods pdf proc report compute block

by Super User in ODS and Base Reporting
‎08-29-2011 05:07 AM
‎08-29-2011 05:07 AM
Because in your column statement , per_osha11 is before per_osha10, but proc report calculated from left to right.So you need use compute per_osha10; to tell sas what the per_osha10'value is. Ksharp ... View more

Re: percentages for a list of variables

by Super User in SAS Programming
‎08-18-2011 02:42 AM
3 Likes
‎08-18-2011 02:42 AM
3 Likes
Almost like _null_'s code: data test; input  q1-q48; cards; 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 ; run; ods output onewayfreqs=freq; proc freq data=test ;   tables q: /nofreq nocum nocol ; run; data temp(keep=tname level percent); set freq(drop=f_: ); tname=scan(table,2); level=coalesce(of q:); run; proc sort data=temp;by tname;run; proc transpose data=temp out=want(drop=_name_) prefix=x ; by tname; id level; var percent; run; data want; set want; flag=input(scan(tname,1,,'kd'),best8.); run; proc sort data=want;by flag;run; Ksharp ... View more

proc report error: adjust column width or line size

by Diamond | Level 26 in ODS and Base Reporting
‎08-02-2011 09:41 AM
6 Likes
‎08-02-2011 09:41 AM
6 Likes
Hi:   Art's memory is correct. That message usually appears because the LISTING destination is still open and the calculated size of a column when added to the calculated size of the other columns will exceed the current LINESIZE setting. The fix is to use ODS LISTING CLOSE; before the ODS step. cynthia ... View more

Re: proc report excel data bars

by Diamond | Level 26 in ODS and Base Reporting
‎03-12-2015 05:33 AM
‎03-12-2015 05:33 AM
Hi, This question is 4 years old.  Please start a new question thread with examples of what you want. ... View more

proc report rbreak summarize

by Quartz | Level 8 in ODS and Base Reporting
‎07-28-2011 12:21 PM
‎07-28-2011 12:21 PM
Cynthia's answer is correct. Here is what the code looks like: computer per_osha; if _break_="_RBREAK_" then per_osha.sum=100; endcomp; ... View more

Re: proc report across variable: change column background color

by Diamond | Level 26 in ODS and Base Reporting
‎07-28-2011 02:09 PM
‎07-28-2011 02:09 PM
Most of the methods boil down to some kind of respecification like this or logic change. But, you could specify things differently. I don't have any missing values for my version of the MDOI variable, but if I use logic to highlight the row if MDOI = "Mar" with my fake data, I do get the entire row for MDOI='Mar' as pink. The trick is avoiding any possible style "collisions" by making sure that you only change the row to pink when MDOI is some value and flipping the logic for the ACROSS items. cynthia compute mdoi;   if put(mdoi,monname3.)='Mar' then      call define(_row_,"style",                        "style=[background=CXE599A7]"); endcomp; ** _c2_, _c3_ are 2010; ** _c4_, _c5_ are 2011; compute msd_tot;   if put(mdoi,monname3.)ne 'Mar' then do;     call define('_c2_',"style","style=[background=yellow]");     call define('_c4_',"style","style=[background=cyan]");   end; endcomp; compute o_tot;   if put(mdoi,monname3.)ne 'Mar' then do;     call define('_c3_',"style","style=[background=yellow]");     call define('_c5_',"style","style=[background=cyan]");   end; endcomp; ... View more

tagsets.excelxp style(header) background color

by Barite | Level 11 in ODS and Base Reporting
‎07-25-2011 03:32 PM
‎07-25-2011 03:32 PM
In a define statement, by default the style option affects both the data rows and the header rows, so the style options on the define statements for oergo1, msd1, and fall1 override the style option on the proc statement. Change those style options to style(column) to match the style options on the other define statements. http://support.sas.com/documentation/cdl/en/proc/61895/HTML/default/viewer.htm#a000146851.htm#a000531789 ... View more

importing an excel with over 1,024 characters

by Opal | Level 21 in SAS Procedures
‎07-15-2011 01:48 PM
‎07-15-2011 01:48 PM
If you are using a libname statement include dbMax_text=32767 in the statement. ... View more

Re: running count by group

by Rhodochrosite | Level 12 in SAS Programming
‎06-29-2011 12:49 PM
3 Likes
‎06-29-2011 12:49 PM
3 Likes
Hi ... try some FIRST. variables ... * leave C1 in the data set to see if logic worked; data test; input id date : mmddyy. job : $1. c1; format date mmddyy10.; datalines; 1 1/1/10 x 1 1 1/15/10 y 2 1 2/2/10 y 2 1 4/1/10 x 3 1 5/1/10 x 3 1 4/2/11 z 4 2 4/3/09 x 1 2 4/6/09 m 2 2 5/8/09 m 2 2 6/8/10 m 2 2 7/8/10 y 3 2 7/8/11 m 4 2 8/8/11 m 4 ; run; * create C2 (should be same as C1); data test; set test; by id job notsorted; c2+(-c2*first.id); c2+first.job; run; * hey, it is !!! ; proc print data=test; run; id         date    job    c1    c2 1    01/01/2010     x      1     1 1    01/15/2010     y      2     2 1    02/02/2010     y      2     2 1    04/01/2010     x      3     3 1    05/01/2010     x      3     3 1    04/02/2011     z      4     4 2    04/03/2009     x      1     1 2    04/06/2009     m      2     2 2    05/08/2009     m      2     2 2    06/08/2010     m      2     2 2    07/08/2010     y      3     3 2    07/08/2011     m      4     4 2    08/08/2011     m      4     4 ... View more

Re: remove last 3 characters

by Opal | Level 21 in SAS Programming
‎06-22-2011 09:40 PM
‎06-22-2011 09:40 PM
Hi If the type is numeric then assigning another format like Ksharp showed would do: format time hhmm5.; HTH Patrick ... View more

Re: data-step label font-size

by Diamond | Level 26 in SAS Programming
‎06-19-2011 04:03 PM
‎06-19-2011 04:03 PM
Hi: TITLE1 and TITLE2 appear to be variables, as are BU, URL1 and URL2. When you use PROC PRINT, either the variable names or labels are used, depending on procedure options. With PROC PRINT, you must use either the LABEL or the SPLIT= option in order to have your variable labels used. Then, in order to alter the default font size of the PROC PRINT output, you must: 1) route your output to a destination that supports style changes (such as HTML, RTF or PDF) 2) use the appropriate STYLE(HEADER)= override in your PROC PRINT code 3a) decide whether you want all the headers the same size or 3b) decide whether you want different headers different sizes. The program below illustrates the 3b approach. If you wanted ALL the headers to be the same size, then your PROC PRINT code would NOT have style overrides on the VAR statements, but would, instead, have style overrides on the PROC PRINT statement itself: [pre] proc print data=sashelp.class label noobs style(header)={font_size=18pt}; [/pre] cynthia [pre] ods html file='c:\temp\large_labels.html' style=sasweb; proc print data=sashelp.class(obs=3) split='*' noobs; var name / style(header)={font_size=18pt vjust=b} ; var age / style(header)={font_size=10pt vjust=b}; var height weight / style(header)={font_size=24pt vjust=b}; label name = 'Student Name' age = "Updated on*June 19, 2011"; run; ods html close; [/pre] ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎08-23-2020 05:17 AM
Likes given to
View All
Likes from
Quick links