Hi,  As previously suggested by others, it appears the editor is not recognizing the program.  Since you mentioned that if you copy the code into a new program window it shows the Enhanced editor colors.  Have you tried saving that program and then opening the new one.       Perhaps there are some unusual characters in the original program that are preventing SAS from understanding the text.   Thanks, Mary   ... View more

Hi, It does appear to be a quoting or macro quoting issue, however given it is happening in ALL your programs it would appear that something has changed in your SAS Environment.  If you are using SAS EG, did you or someone add custom code in SAS Enterprise Guide inserted before code submission?  Perhaps an autoexec program has changed, but this would generally impact only the first program.  What SAS Environment are you using?   Did you change from a windows environment to a UNIX environment and some unusual characters where inserted when moving to the different O/S?   By the way use this code to correct possible unbalanced quotes  '*;"*;run; Note: It may not correct all macro quoting issues, which would need a SAS reset. Mary       ... View more

Hi Juli4, Your code does match the solution, and to double check I copied your code, ran it and I did get the correct results.  There could be an issue with the input table.   Did you see the following NOTE in your log? NOTE: There were 384 observations read from the data set PG2.NP_MONTHLYTRAFFIC. WHERE ParkName='Cuyahoga Valley NP'; Thank you Mary ... View more

Hi SASAna, The below program looks for the values  1234,2345,4567,8903 in the column Code.  The first Data Step creates the test data set. Let me know if I have misunderstood your question.   Thanks Mary   data new; input code $; datalines; 1234 2345 4567 5464 8903 2090 1234 1234 ; run; %let procs=1234,2345,4567,8903;   data find;  set new;  do i= 1 to 4;    if code=trim(scan("&procs",i,',')) then output;  end; run; ... View more