So this step: PROC SUMMARY data=mylib_d3.covid_data mean print; BY continent date; VAR new_cases new_deaths; output out=mylib_d3.mean_cas_deces mean=mean_nouveaux_cas mean_nouveaux_deces; RUN; Will create one observation per CONTINENT DATE if you want to find the MIN/MAX of those MEAN values you will need to eliminate one of the BY variables.  For example if you eliminate DATE from the BY statement you will get the MIN and MAX of the daily means per CONTINENT: PROC SUMMARY data=mylib_d3.MOYENNE_CAS_DECES min max print; BY continent ; VAR moyenne_nouveaux_cas moyenne_nouveaux_deces; output out=mylib_d3.min_max_cas_deces min=min_nouveaux_cas min_nouveaux_deces max=max_nouveaux_cas max_nouveaux_deces ; RUN;   ... View more

@Astounding wrote: A good rule of thumb is to get your program working without macros first, and then try to convert it to a macro.  It's too difficult for a beginner to debug if you have to figure out whether your error comes from SAS language or macro language. This is so important, I am going to repeat it.   "A good rule of thumb is to get your program working without macros first, and then try to convert it to a macro.  It's too difficult for a beginner to debug if you have to figure out whether your error comes from SAS language or macro language." If you can't get the code to work without macros and without macro variables, then it will never work when you use macros and macro variables. ... View more

I won't bother with the data you posted as an attachment, but this is a good situation for running a proc freq on a subset of the original data, and then running a proc freq and the results of the first proc freq:   proc freq data=myhlib_d3.nb_deces noprint; where new_deaths>=1; table date*iso_code / out=need (keep=iso_code date); run; proc freq data=need; tables iso_code /out=want (keep=iso_code count); run; Note that the WHERE filter can be applied in the first proc freq, so you don't need to run a preparatory DATA step.   The first proc freq writes an output dataset NEED.  It would ordinarily have 4 variables: iso_code date count and percent.  But you only need the iso_code and date variables.    Then the second proc freq is applied to dataset need, giving a frequency of each iso_code, i.e. then number of unique date values encountered per iso_code.   This is a good example of using the power of various proc's instead of data step programming. ... View more

PROC FREQ produces counts ... View more

The asterisk in front of the program name suggests that the program contents have been changed but not saved. What happens if you do a Ctrl-Z to undo the last change? Do your previous contents appear?   Alternatively close EG without saving the program, then reopen EG and try reading the program again. ... View more

Is that the full code you ran?   That wouldn't be valid, you ned to wrap your code in a proc or data step for starters.    If it isn't the full code, please post the actual code and indicate what errors you received or why you think it isn't working. As @AlanC indicated the case does need to match as well.    proc sql; delete from d1.covid_data where lowcase(location) = 'world'; quit; @Feksan wrote: Hello. I would like to delete the rows where the location is "World". This is my code and it doesn't delete it.   DELETE FROM d1.COVID_DATA WHERE location="world";   ... View more

You need to put commas in between variables in a list in SQL (unlike in normal SAS code where you use spaces).  N items will require N-1 commas. So if there are three items you need two commas.  If there is only one item then you need zero commas. SELECT * FROM d1.owid_covid_data_2019 ... If will help you limit the number of times you make mistakes with missing/added commas if you get in the habit placing the commas at the beginning of the continuation line instead of at the end of the line you are wrapping.  This will make it easier for you to notice when scanning the code since you don't need to move your focus left and right. SELECT A.iso_code , A.continent , A.location AS pays ...   ... View more

Maxim 3: Know Your Data. There is no variable moyenne_globale in your dataset. Run a PROC CONTENTS on d1.COVID_DATA to determine which variables are contained in it. ... View more

You need to put commas in between variables in a list in SQL (unlike in normal SAS code where you use spaces).  N items will require N-1 commas. So if there are three items you need two commas.  If there is only one item then you need zero commas. SELECT * FROM d1.owid_covid_data_2019 ... If will help you limit the number of times you make mistakes with missing/added commas if you get in the habit placing the commas at the beginning of the continuation line instead of at the end of the line you are wrapping.  This will make it easier for you to notice when scanning the code since you don't need to move your focus left and right. SELECT A.iso_code , A.continent , A.location AS pays ...   ... View more