The solution I'm about to propose is not as efficient as the hash solution by Ksharp, I just think that it's a fun way to approach the problem.  If the data set is large and efficiency is a concern, then I would have also used a hash solution.  Before executing my solution, you have to first create a user-defined function with PROC FCMP, which is a one time endeavor.  I call this the SQL function.  After it is created, you could use this function in any program. To create the function, you need to first save the following macro in your autocall library: %macro sqlfunc;      %let sqlselect = %sysfunc(dequote(&sqlselect));      %let sqlresults = ;      proc sql noprint;           create view _TempView_ as &sqlselect;           select * into: sqlresults separated by " " from _TempView_;           drop view _TempView_;      quit;      %let sqlresults = &sqlresults; %mend; Next run the following FCPM procedure: proc fcmp outlib=sasuser.funcs.general;      function sql(sqlselect $) $;      length sqlresults $ 32767; /* NOTE THAT IF YOU ARE USING SAS 9.2, THE LARGEST LENGTH YOU CAN USE HERE IS 260 */      rc=run_macro('sqlfunc', sqlselect, sqlresults);      return(sqlresults);      endsub; quit; Now you need to set the CMPLIB= option to tell sas where to look for previously compiled functions.  I recommend doing this in your config file. options cmplib=sasuser.funcs; Now that the function has been defined, here is my solution to the problem: data %sysfunc(sql(select distinct name from have));      set have;      array subjects{*} _numeric_;      do i=1 to dim(subjects);           subject=vname(subjects{i});           mark=subjects{i};           %sysfunc(sql(select distinct catx(' ', 'if name =', quote(strip(name)), 'then output', name, ';') from have));      end;      keep subject mark divison; run; Note that you could also use the SQL function in an expression or an assignment statement within the DATA step, without using %SYSFUNC.   ... View more

Thanks Ksharp.   If the macro variable reference is part of an expression or an assignment statement, you can resolve it at execution time using the SYMGET or RESOLVE functions.  For example: %let sex=M; data class/view=class;      set sashelp.class;      where sex=symget('sex'); run; %let sex=F; proc print data=class(obs=3); run; The problem is that I want to use the macro variable in a SET statement instead of in an expression or assignment statement. I know that there are many alternative solutions, such as writing a macro.  I posed the question just out of curiosity, not necessity.  As you said, it might not be possible. Thanks again. ... View more

If you are using the default MAPI email interface, you need to switch to using SMTP email in order to include HTML formatted email in the body of the message. ... View more

Cynthia, Sorry about my very belated response to this thread.  I was able to do some DATA step post-processing on the XML code to modify the style elements that you pointed out.  I just wanted to says thanks again for all the help and to offer a potential solution to this problem for anyone who might be interested. ods listing close; ods tagsets.excelxp file='class.xls' style=sansprinter; proc report data=sashelp.class nowindows;      column name sex age height weight; run; ods tagsets.excelxp close; ods listing; /*** Store the new XML style definitions for StrikeThrough cells in a data set. One style definition is created for left-aligned data      and one style definition is created for right-aligned data. ***/ data strikethrough_styles; length line $ 200; infile datalines truncover; input line &; datalines; <Style ss:ID="StrikeThrough_L" ss:Parent="data"><Alignment ss:WrapText="1" ss:Horizontal="Left"/><Font ss:StrikeThrough="1"/> </Style> <Style ss:ID="StrikeThrough_R" ss:Parent="data"><Alignment ss:WrapText="1" ss:Horizontal="Right"/><Font ss:StrikeThrough="1"/> </Style> ;;; run; /*** Construct a macro variable containing the row numbers to strike through in the spreadsheet.  The number one is added      to the _n_ variable to account for the row in the spreadsheet which will contain variable names. ***/ %let RowNums = ; data _null_;         set sashelp.class;         if name in ('Barbara' 'Jeffrey' 'John') then call symput("RowNums", catx(' ', resolve('&RowNums'), _n_+1)); run; data xml_code (keep=line);         /*** Read the XML code from the spreadsheet ***/         length line $ 200;         infile 'class.xls' truncover;         input line &;         /*** The line </Styles> denotes the end of the style definitions.  Once this line is encountered, add the two new style              definitions we defined previously.  ***/         if strip(line) = '</Styles>' then do;                 do until(eof);                         set strikethrough_styles end=eof;                         output;                 end;                 line='</Styles>';                 output xml_code;         end;         else do;                 /*** Lines that begin with <Row denote a new row.  Increment the row number counter by one. ***/                 if substr(line, 1, 4) = '<Row' then RowNum + 1;                 /*** Apply the a new strikethrough style if a cell is being defined in one of the previously established row numbers.              Numbers will be right-aligned and strings will be left-aligned.  The names of the new style definitions will overwrite                      the values which were previously defined in the StyleID attribute. ***/                 if substr(line, 1, 5) = '<Cell' and RowNum in (&RowNums) then do;                         if find(line, 'Type="Number"') then line=tranwrd(line, scan(substr(line, find(line, 'StyleID=')+8), 1, '"'), "StrikeThrough_R");                         else if find(line, 'Type="String"') then line=tranwrd(line, scan(substr(line, find(line, 'StyleID=')+8), 1, '"'), "StrikeThrough_L");                 end;                 output xml_code;         end; run; /*** Recreate the spreadsheet using the modified XML code. ***/ data _null_;         file 'class.xls';         set xml_code;         put line; run; ... View more

Here is an easy solution that does not use regular expressions. data test; comment = 'Blah blah Blah "Dont need this" yada yada yada "Definately need this" so forth and so on...'; quote=scan(comment, -2, '"'); run; ... View more