The enhanced editor key combination of Ctrl ( when the cursor is placed on a paranthesis, bracket or brace will find the matching one. If the cursor doesn't move then it is unbalanced. ... View more

The error message is from this line expression: Account__ = . Suppression of that error message is why I reversed your logic.  My example will generate the variable LN_NO for all values of account. The ?? in front of the INFORMAT will suppress the error message. The other advantage of doing the PUT() function first is that if LN_NO is not defined in the input dataset then SAS will know to create it as a character variable of length 10 based on the use of Z10. format. If the value in ACCOUNT__ is invalid then the INPUT() function will return missing and the PUT() function should spit it out as a period in position 10. (depending of the setting of the option MISSING).  So the COMPRESS() function will convert the period to a space. You might need more complex logic if the variable ACCOUNT__ is longer than $10.  Using INPUT(ACCOUNT__,10.) will only read the first 10 characters.  So if ACCOUNT__ is twelve digits long it will ignore the last two, so '000000000100' would be converted to 1 instead of 100. ... View more

You'd better post some sample data and output you need. That would be better . from your description It seems that you need a having clause. group by ln_no    having pmt_due_dt=max( pmt_due_dt) ; Ksharp ... View more

FWIW, Finally I bumped into something from SAS-L regarding this matter: Quote from one of Lassen's recent posts: " as the macro language interpreter evaluates it like this 1<0<2 -> (1<0)<2 -> 0<2 -> 1 " Which means macro language evaluates expressions in a segmental pattern, not as a whole. It is not necessarily causing error message, it just interprets it differently, therefore leads to unexpected results. So as long as you know know how exactly it works, you can still use it in Macro language. Haikuo ... View more

A fast way, if you need the final observation in the entire data set: data want;   set have point=_nobs_;   output;   stop;   set have nobs=_nobs_; run; Good luck. ... View more

Hi:   I believe you will need to use CALL DEFINE in a COMPUTE block to specify a different format when you have a zip+4 versus just a zip code (based on the length of the data value). cynthia data testzip; length name $12 zip_cd $9; infile datalines; input name $  zip_cd $; return; datalines; alan 300112222 barb 202113333 carl 20022 dave 00221 edna 003334444 fran 777 ; run;    ods tagsets.excelxp file='c:\temp\zipcode.xml' style=sasweb;   proc report data=testzip nowd;    column name zip_cd;    define name / order;    define zip_cd / display "Zip Code";    compute zip_cd;       lgzp = length(zip_cd);       if lgzp = 9 then do;         call define(_col_,'style',                     'style={tagattr="format:00000\-0000" cellwidth=80pt just=center}');       end;       else if lgzp le 5 then do;         call define(_col_,'style',                     'style={tagattr="format:00000" cellwidth=80pt just=center}');       end;    endcomp;    run;     ods tagsets.excelxp close; ... View more

check that your filename.extension of .xlsx is in alignment with dbms=Excel SAS/ACCESS(R) 9.3 Interface to PC Files: Reference Microsoft Excel Workbook Files ... View more

Here are some references on Evaluating Logical Expressions http://www.sascommunity.org/wiki/Evaluating_Logical_Expressions This is the support.sas page on order of precedence of evaluation of logical operators Defining Arithmetic and Logical Expressions SAS(R) 9.3 Macro Language: Reference Ron Fehd  logically yours ... View more

Could you please tell us some more information about your task? DO you need a hint about how to join 4 tables (which provided by DBeily), or you need a way to do it based on a certain conditions? p.s. By the way ((IF Prop_Type NE 2  OR If Prop_Type EQ 2 and Disburement NE 250)) == ((IF Prop_Type NE 2  OR  Disburement NE 250)) since (not x) or x and y == (not x) or y ... View more

We cannot see the end of your macro to see how you are making the report itself.  Most likely you want to create the WHERE in the DATA step so that it has all the appropriate dates.  You can also eliminate your DATA _NULL_ step. %let lastddate = %sysfunc(intnx(Month, %sysfunc(TODAY()), &n)); %let startdate  = %sysfunc(intnx(Month, %sysfunc(TODAY()), %eval(&n-1))); the WHERE becomes something like: where &startdate le date le &lastdate; But until we know more of what you need these are guesses. ... View more

Hi,   As Reeza suggests, you cannot append to a TAGSETS.EXCELXP XML file once you have closed it. My rule of thumb when working with macro programs is to start with a working SAS program, so you know what kind of code your macro program has to generate For example, if you had tried to create a 2-tab workbook, you could have done it in one ODS "sandwich" with one procedure step creating output for the first tab, and the second procedure step creating output for the second tab (taking all the defaults). Generally, this means code similar to the code shown below, which creates a multi-sheet workbook. Once you get code like this working for your report, then, and only then, should you look to "macro-ize" your code. It doesn't help to macro-ize non-working code, that is nearly impossible to debug. cynthia ods tagsets.excelxp file='c:\temp\multsheet.xml'     options(doc='Help' sheet_name='Starts with J')     style=sasweb;    proc  print data=sashelp.class noobs;   where substr(name,1,1) = 'J'; run;   ods tagsets.excelxp options(sheet_name='Starts A, B, C');    proc print data=sashelp.class noobs;   where substr(name,1,1) in ('A','B','C'); run; ods tagsets.excelxp close; ... View more

Hello Omega1983, A solution could be to exclude the Code1 variable including (1) and (6) into the Drug variable and then use the following code: Drug=SUBSTR(Drug,ANYALPHA(Drug)); that excludes (1) and (6) or anything else up to the first letter in the Drug variable. Sincerely, SPR ... View more

SPR My bust you are correct For those in the forum see the below code as a demostration data s1(drop=s2) s2(drop=s1); set sashelp.shoes; inS1=1; inS2=1; run; %macro overall; data one; %let Region='Africa'; if Region=&region then set %do i=1 %to 2; s&i %end; ; run; %mend overall; %overall; ... View more