About HN2001

Cynthia_sas · ‎11-10-2023

Hi: ODS ESCAPECHAR to the rescue. For most ODS destinations, you can use ODS ESCAPECHAR to insert style overrides for pieces of a string. This is easier to do in a DATA step before your reporting step so that you can use the SCAN, SUBSTR and CAT functions to rebuild the string with the ESCAPECHAR overrides. Here's an example: This works in ODS HTML and ODS EXCEL, as shown above. I added the colors with the bold, so the changes would stand out in the screen shot. Of course, this does assume that the strings 4dr and 2dr are all you're looking for and that the string is exactly 3 characters long and that by the first word, you meant the first "chunk" of the Model variable up to the first space in the value. Cynthia

HN2001 · ‎08-09-2023

Tom - Thank you so much for your help! It cleaned up the log and still gave me the output I was looking for! Thanks again

PaigeMiller · ‎03-21-2023

This should help PROC REPORT — different formats for different rows? - SAS Support Communities

data_null__ · ‎03-10-2022

I'm on a PROC SCORE kick. You need a custom SCORE data set like this. Which you can generate with iterative DO. data have; infile cards expandtabs; input Group:$2. Day1-Day4; datalines; G1 2639 2639 2645 2671 G2 3079 3503 3554 3620 G3 285 291 358 379 G4 9434 9510 9570 9690 G5 13182 13525 13548 13902 ;;;; run; data score; if 0 then set have(keep=Day:); array v[*] _numeric_; retain _TYPE_ 'SCORE'; length _name_ $32; do i = 1 to dim(v); call missing(of v[*]); v[i]=-1; do j = i+1 to dim(v); _name_ = catx('_',vname(v[i]),vname(v[j])); v[j] = 1; output; v[j] = .; end; end; drop i j; stop; run; proc print; run; proc score data=have score=score out=diffs; id group day:; var day:; run; proc print; run; And SCORE using PROC SCORE.

JuanS_OCS · ‎09-03-2020

Hello @HN2001 , this seems to a problem with the SASDM, the Enhanced Editor on Windows. I have seen this issue in the past due to several reasons. I could imagine there is something wrong on a library (mainly when you use a non-English language/locale) or the Windows Registry. I would suggest the following approaches, in order. If one works, you won't need to take the following ones: 1- Check the latest hotfixes available for your installation, and install if any is relevant to your issue. 2- Reinstall SAS 3- Check the following SAS notes https://support.sas.com/kb/15/185.html https://support.sas.com/kb/38/222.html https://support.sas.com/kb/18/120.html https://support.sas.com/kb/33/427.html 4- Contact SAS Tech Support Of course, you can contact SAS Tech Support right away, the steps are only there because perhaps they could give you quick solutions to your problem.

ballardw · ‎08-21-2020

Show the different sort codes used and the proc corr. Best would be to show it from the log with notes about records used. I responded about the order of the With and Var pairing because your example code does not show any sort involving either of those two variables. Since the example that you show is not sorting either of the With or Var variables and is using a BY statement then if you sort the data by different variables with different BY statements then I would be extremely surprised to see the same result for almost anything. And since you only show one "example" we really need to see the other to compare.

Ksharp · ‎09-26-2018

data have; infile cards truncover; input Final_Decision $ ItemType $ Time; cards; Keep Type1 2 Keep Type1 3 Keep Type1 2 Keep Type2 4 Exclude Type2 9 Keep Type2 3 Keep Type1 2 Exclude Type1 11 Keep Type2 1 Exclude Type2 10 Keep Type2 2 Keep Type1 3 Keep Type1 3 Keep Type1 4 Keep Type1 5 Keep Type1 3 ; proc sql; create table want as select ItemType,count(ItemType) as totalitems, sum(Final_Decision ne 'Exclude') as number_not_excluded from have group by ItemType; quit;

HN2001 · ‎06-20-2018

thanks Cynthia. I wasn't using the tagsets but ended up formatting the variable again to make sure it was character and it worked. thanks again for the idea of formatting.

HN2001 · ‎06-20-2018

Try the solution in this link https://communities.sas.com/t5/ODS-and-Base-Reporting/ODS-excel-amp-multiple-sheets/m-p/261953/highlight/true#M15551 there is a bug and you have to create a dummy table code to make this work and put each output on it's own tab

HN2001 · ‎03-23-2018

I agree I am definitely seeing limitations with libname excel and libname xlsx, even using proc import I see variations in how the data is read in with xlsx and excel

HN2001 · ‎03-22-2018

Using a # helped with the . in the name "AB# ADD"n='char(13)'

Online Status	Offline
Date Last Visited	‎11-10-2023 05:36 PM

Highlighting part of string value in proc report column

Re: Need ampersand to act as the actual value and SAS not think it is ...

Re: Need ampersand to act as the actual value and SAS not think it is ...

Need ampersand to act as the actual value and SAS not think it is a ma...

Formatting proc report in different rows and columns

Re: Differences for continuous columns

Differences for continuous columns

Re: Automated error when opening sas program

Automated error when opening sas program

Re: Proc corr polyserial

Re: Highlighting part of string value in proc report column

Re: Need ampersand to act as the actual value and SAS not think it is ...

Re: Differences for continuous columns

Re: Char length being truncated

Re: Differences for continuous columns

Differences for continuous columns

Automated error when opening sas program

Re: Automated error when opening sas program

Re: Highlighting part of string value in proc report column

Re: Need ampersand to act as the actual value and SAS not think it is ...

Re: Formatting proc report in different rows and columns

Re: Differences for continuous columns

Re: Automated error when opening sas program

Re: Proc corr polyserial

Re: proc sql using where clause

Re: Commas not being maintained from sas proc print to excel

Re: ODS EXCEL multiple sheets for each iteration in a macro

Re: Char length being truncated

Re: how to write DBSASTYPE code for excel column names with symbols