@jawhitmire wrote: Thank you for the quick reply.   I would like to flag each constituent with a warning.   That is, create a macro variable that is blank when there is no warning, but prints the name of the constituent when conversionfactor is . or when PrimaryResultsCount<6.   The macro will later be referenced in an executive summary.   Thanks again, Jane How are you creating the executive summary? If it is to create a list of those with a flag set then consider:   data want; set sashelp.class; if sex='F' then weightflag= weight>90; else if sex='M' then weightflag= weight>110; run; Proc print data=want noobs; where weightflag; title "Names of children with Weight Flag set"; var name; run;title; The rules for weightflag were very arbitrary just to create the flag variable as a dichotomous 1/0 coded value. Select the values to display with a where clause for example and Var to show the values you need for your summary.   Better might be to provide some example data in the form of data step code and how you want the executive summary to appear. There are LOTS of things that can be done with properly structured data and report procedures. Stuffing lots of values into macro variables is quite often the most difficult to get nice output from.   Instructions here: https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-data-AKA-generate/ta-p/258712 will show how to turn an existing SAS data set into data step code that can be pasted into a forum code box using the {i} icon or attached as text to show exactly what you have and that we can test code against.   ... View more

@Kurt_Bremser wrote: The double ampersand forces two passes; in the first pass, the double ampersand is resolved to a single one, and macro variables within the string are resolved; in the second pass, the whole construct is resolved. This method can be expanded by using even more consecutive ampersands.   And ever more obscure code.   Yes I've done that. And now look for alternate approaches as if I don't look at the code for awhile I don't remember why &&&&This&&var&mess was a good idea. ... View more

Thank you. It works perfectly. Cheers! ... View more

IF lastone THEN DO; call missing (A,B,C,term); additup=cum_soln; output; END; Call missing is one of the few data manipulation functions that will work on both character and numeric variables and all at the same time. ... View more

Hi Cynthia,   Thank you for the assistance with SAS ODS.   Do you have an example to share?   Jane ... View more

Tom, Wow - something complicated made simple.  Thank you! Jane ... View more

Thank you for the feedback. This was the perfect solution. Jane ... View more

Oh yes, it would be wonderful to use "proc score" - but it appears it requires the SAS/STAT library. Without this and without SAS/IML, it sometimes feels like re-inventing the wheel. Very happy to have assistance from the SAS Community. Thank you for the reply. Jane ... View more

Since you are not really "merging" on anything why not just use two SET statements? Place the ARRAY between them. data want ; set have; array all _numeric_; set fix (keep=fix); do over all; all=all*fix; end; run; I know that SAS is trying to make DO OVER go away, but it is so much more logical than having to invent an index variable that has no intrinsic meaning.   Of course the real question is why doe the Original user need to multiply the values? Perhaps they just need to use the variable FIX with a WEIGHT or FREQ statement in their analysis. ... View more

Since you are not really "merging" on anything why not just use two SET statements? Place the ARRAY between them. data want ; set have; array all _numeric_; set fix (keep=fix); do over all; all=all*fix; end; run; I know that SAS is trying to make DO OVER go away, but it is so much more logical than having to invent an index variable that has no intrinsic meaning.   Of course the real question is why doe the Original user need to multiply the values? Perhaps they just need to use the variable FIX with a WEIGHT or FREQ statement in their analysis. ... View more

I know there are already several good solutions here, but there's a technique that should not be overlooked.   filename recode 'path to some file'; data _null_; infile datalines; input name $ fix; file recode; put name '=' name '*' fix ';' ; datalines; sam 0 david 3 karen 4 mike 8 ; That creates a file holding all the recoding equations.  Then:   data want; infile datalines; input sam david karen mike; %include recode; datalines; 5 7 8 4 6 4 8 9 7 3 2 6 ; ... View more

Thank you for the quick reply.   The information at the link was informative and the following correction fixed the problem.   proc sql; create table work.addcompounds2GFC(compound2 char(3), GFC_Suc_MPB num, Final_Weigh_SD num); insert into work.addcompounds2GFC values('S',0,0) values('Cl',0,0); Thanks again. Cheers!   Jane     ... View more

This worked perfectly and the output is clean.  It seems my questions are slowly becoming a bit more difficult.  I look forward to the day when I can contribute as much as I ask. Thank you! Jane ... View more