Outer joins get a little tricky if you have Where conditions for columns that come from the [dependent] table. If a table does not contribute attributes for a row in the result set, its resulting columns are null. Therefore, your where clause must accommodate such behavior (see coalesce function). ... View more

See SAS online documentation: Restriction: Even though a character string or character variable is accepted, only the first character of the string or variable is used as the output delimiter. This differs from INFILE DELIMITER= processing. ... View more

I think the clue is located in [checking Record ID]. You are reading from a relational database, like DB2 which allows dates like 08/08/0018, whereas noted earlier, SAS only goes back to 1582. If you check your log, (not sure if that is possible/easy in EG), you would probably see a note like: NOTE: The data value for column DATE1 (DATE1) was truncated or was out of range 1 times when retrieving that data from the DBMS. That's what caused your missing value. I just verified this with PC/SAS 9.1.3 and DB2. So, the real question is...Is that a data entry error or do you have to figure out an alternate method for handling really old dates? ... View more

ods rtf prepage='\R/RTF"\s1 " Names; run; You're missing a single quote somewhere on the line above, but I doubt that will "fix" your problem. ... View more

Change last data step to: data result; set read(drop=system_defect); by system defect; if first.defect then count=0; count+1; if last.defect then output; run; ... View more

David has an excellent idea. Try: 1 data _null_; 2 sqrt = 2**(-.5); 3 put sqrt;run; 0.7071067812 ... View more

try adding the PROC SQL feedback option to your code rather than MPRINT. like: proc sql feedback; /* etc */ or use options symbolgen. ... View more

Try something like: Data Step2; set step1; result = var1/var2; run; proc transpose data=step2 out=step3(drop=_:) prefix=Result; by date; var result; id obs; run; proc print data=step3; run; ... View more

Try adding content_type to the attach= options. I believe that the shortcut (.lnk) is actually a binary file. I've had success in the past referring to binary files as image files. So try something like: filename SendMail email to=(&macvar.) subject="SAS Processing : Duplicate Party Records Report" attach=("\\svrbu3file\shared\public\Inf_Mgt\Projects\Data Quality\Reporting\Exception Reports\Shortcut to Issue 158 - Duplicate party records.xls.lnk" content_type="IMAGE/GIF") type='Text/Html' ; ... View more

Why don't you like to depend upon the "dictionary" tables? Unless you are using where clause in a proc or data step, the information provided by the dictionary tables is as good as SAS is. ... View more

Stick with the JOIN syntax and try something like From WORK.VIEWLIFESTYLEREPORT inner join WORK.GROUPCLH on viewlifestylereport.common_key = groupclh.common_key Left join WORK.VIEWLIFESTYLEGROUPS ... View more

Chuck, your approach doesn't guarantee that a row could be selected multiple times, does it? ... View more

How about using PROC SURVEYSELECT? proc surveyselect data=subscribers out=subsamp100(drop=selectionProb samplingWeight) method=srs /* simple random sample */ n=100 /* 100 per strata */ noprint seed=1952 ; *strata prodlvl1d /* stratified by product level 1 */; run; ... View more

Is that actually a character variable with a blank and a period or a character variable with just a period in it? Really it doesn't make any difference the period is used to indicate missing data for numeric data. A character variable with a period is not a missing value, a character variable that is blank can be (is) considered missing. So, if it is a character variable, you would exclude it as where var ne " ." or where var ^= " ." ... View more

In your second macro definition, try: %macro loop_vals(lval=g_dist,delim=*); instead of %macro loop_vals(lval=&g_dist,delim=*); ... View more