All macro variables are stored as strings.  What behavour (error message etc) are you seeing that makes it numeric. http://support.sas.com/documentation/cdl/en/mcrolref/61885/HTML/default/viewer.htm#a002293823.htm   You can see from this log that if we try to store a numeric in a macro var it is converted to char by SAS.   1 data null; 2 call symput('currmonS',put(date(),yymmn6.)); 3 call symput('currmonN',date()); 4 run; NOTE: Numeric values have been converted to character values at the places given by: (Line) : (Column). 3:28 NOTE: The data set WORK.NULL has 1 observations and 0 variables. NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.01 seconds . ... View more

You'd better post it at ODS and Report forum, since it is a question about proc report. and Cynthia is there. Code: Program.sas data Have; input var1 $ var2 $ var3; cards; aaa c 52 XXX a 678 XXX b 126 XXX c 118 XXX d 46 XXX e 164 XXX f 13 CCC a 1056 CCC b 642 CCC c 1368 CCC d 596 CCC e 694 CCC f 21 y a 223 y b 222 ; proc report data = Have nowd out=x; define var1/group; define var2/group; define var3/analysis sum; compute var3; if _BREAK_='var1' and var1='XXX' then s=var3.sum; endcomp; compute after; var1='Total'; dif=var3.sum-s; line 'Total without XXX:' dif best32.; endcomp; break after var1/summarize; rbreak after/summarize; run; Xia Keshan ... View more

Use the intnx function to return the same day of the previous month: intnx('month',datevar,-1,'s'). SAS designed this very intelligently for month's with 31 days.  In the event that the previous month does not have as many days, it will default to the end of the month.  So running this with a current date of 3/29/2014 would return 2/28/2014 as the same day from the previous month. Then, rather than build your own string, just use the date11 format: data _null_;                 dd = day(today());                pd = intnx('month',dd,-1,'s');               CALL SYMPUT('bur_str_m1', "'"||put(pd,date11.)||"'");    run; ... View more

data have; input ACCT FLAG; cards; 14710 1 14710 0 14710 1 49730 1 49730 0 49730 1 15293 1 15293 1 1147  1 1147  0 1147  0 13664 1 13664 1 13664 1 ; run; proc sql; create table want as   select * from have where flag=0    union all   select distinct * from have group by acct having sum(flag=1)=count(*); quit; Xia Keshan ... View more

Your problem is not stated very clearly, so I made some assumptions. For every acct you want: 1) the record with the highest priority 2) in case of a tie in priority, the record with dst = "N" 3) in case of a tie in priority and dst, the record with timezone="Mountain" 4) in case of a tie in priority, dst and timezone, any one of the tied records proc sql; create table b as select unique * from a group by acct having priority+(dst="N")/2+(timezone="Mountain")/4 =   max(priority+(dst="N")/2+(timezone="Mountain")/4); select * from b; quit; PG ... View more

I'm not familiar with SAS BI Dashboard, but there is some how-to docs in the SAS Knowledge Base (and other docs on the web) that could point you in the right direction. Here is a sample at http://support.sas.com/kb/34/704.html (applies to BI Dashboard 4.2). Reading the instructions, it appears that you need to have libraries defined (e.g. the SASHELP library used in the example must be defined first). That would be consistent with how SAS functions in all of their other products. Here also is a link to their BI Dashboard Guide (v. 4.3) http://support.sas.com/documentation/cdl/en/bidbrdug/63081/PDF/default/bidbrdug.pdf ... View more

If you're referring to Gady's post, that very likely only would work on XLSX (I wrote roughly the same thing a year ago, and FriedEgg wrote a simpler routine as well).  XLSX is an xml file, XLS may be a binary file (it also may be a very differently structured XML file). ... View more

I don't know if your question was a general one or if that program exists in the context of something else. The following would get rid of the error but may not be optimal depending on what else you're doing. Recently I've been creating empty datasets that I use as a base on which to append when looping a macro repeatedly and creating similar outputs that I want to be in one dataset, but do not want to have to write them all out into one set statement. So, before that data step you could have: data WORK.AIR201310;      attrib VARIABLES AND ATTRIBUTES HERE;      stop; run; ... View more

I would talk to your SAS sales rep for that sort of information.  They should have specific information related to the products and uses you have. ... View more

Am I missing something here? This is what I understand a pure Oracle issue, and would be better discussed on an Oracle forum. ... View more

Is this a case where linguistic sorting might help? Recently introduced, proc sort sortseq=linguistic( ) And something about number sorting to ensure xxx10 comes after xxx9 ... View more