Before starting on using the macro processor to generate some SAS code you need to be clear about what SAS you need to generate.   Can you explain a little more about what code you are trying to create?   For example you mentioned that you were able to get this code fragment to work. data SAMP ; set VAMP; where sampdate ge &Qstart. ; run; That will work when value of the macro variable QSTART is text that will make the syntax of the WHERE statement valid.  So if SAMPDATE is numeric variable with DATE values then any text that looks to the SAS compiler like a valid date value should work.  So you could have QSTART set to things like: %let qstart="01JUL2025"d; %let qstart='01-jul-2025'd; %let qstart=mdy(7,1,2025); %let qstart=intnx('qtr',date(),0,'b'); %let qstart=23923; The first two are date literals.  The next two are expression that SAS will evaluate to a date value. The last one is the actual number that SAS uses to represent the first of July in the year 2025.   Note that to the macro processor all of them are just text strings. ... View more

Looks like you have several good answers. However, it is also very helpful to us (and therefore helpful to you) if you explain what the macro is supposed to do, like I asked. Please keep that in mind in your future questions. ... View more

thank you! ... View more

Hi Paige, thanks a lot for reply, so in most cases, split table is not necessary, unless one really need to do so. ... View more

Use IF when you need to filter based on new or transformed variables. Use WHERE when filtering on existing dataset variables, and in PROC steps, for better efficiency. note: With IF, this upcase() runs before filtering, so lowercase “a” and “b” are converted, then kept. With WHERE, the condition is evaluated before upcase(). Since it checks the original values, lowercase “a” or “b” will not match and get dropped.   That's why you get different obs number with where and if.   incase of missing data- data results.output36; set cleandata36; if Kilograms = '.' or 40>Kilograms or Kilograms>200 then do; if group='A' then Kilograms=79; else Kilograms=89; end; run; ... View more

In a DATA step, use by usubjid; At first.usubjid, set join to 1. If not first.usubjid, and either ae is not equal to lag(ae) or aestdtc is greater than lag(aendt), increment join by 1. ... View more

Normally in that case you would use MERGE statement in a data step. data fixed; merge original updates; by key vars ; run; Although you might want to use the orignal UPDATE statement (that has nothing to do with the SQL statement with the same name).  That is designed to apply transactions.  That way you only need to enter the values that change in the transaction dateset since with UPDATE missing values do not replace the original value.  So you only need to enter the values that need to change. ... View more

/* UNTESTED CODE */ data have; set have; id=1; run; data want; update have(obs=0) have; by id; output; run; ... View more

For more on means models, see the first volume of Analysis of Messy Data by Milliken and Johnson. It is just a different way of parameterizing a linear model that is particularly useful for unbalanced datasets. Any of the SAS procedures that allow CLASS statements or implement dummy coding can be used.   As far as a definition for "moderator",  Mr. Google offers "In statistics, a moderator variable (or simply a moderator) is  a third variable that influences the relationship between two other variables ." In this case, it appears that weed cover is a moderator in the relationship between yield and treatment. It is a variable that you don't control in the design. It really works better for continuous variables, but it appears for categorical interactions as well.   SteveDenham ... View more

@Mscarboncopy - I suggest you also include @ChrisHemedinger 's link: Changes to SAS Authorization Codes (SETINITs) in your response. The important thing to note is you get your licence files at the START of your invoicing process (the Purchase Order step) and not at the END when it is actually paid, saving several weeks.  ... View more

This support note has some suggestions: https://support.sas.com/kb/61/382.html   But agree with Paige, first step is probably to run PROC CONTENTS to make sure that variable does not have a format attached. ... View more

  @sathya66  When I first posted the code for DATA WANT; I left two lines out, that is now corrected in my reply above, but you need to modify your code to show those changes I made. ... View more

Try tagsets.excelxp destination.  As discussed in this paper, it handles memory differently than the EXCEL destination.   https://support.sas.com/resources/papers/proceedings16/SAS5642-2016.pdf     ... View more

I am a SQL guy, just for having some fun . data x; do year=2001 to year(date()); output; end; run; proc sql noprint; select year into :yearlist separated by ' ' from x; quit; %put &=yearlist.; ... View more