@elmendamian you need to do something like this to convert your stringed macro date to a number that represents SAS date values. %let mydate = 10dec2019; data _null_; yesterday = input("&mydate",date9.); put yesterday; run;     ... View more

Post what you have so far then and we can help you out with it from there. ... View more

If you're on Windows then take a look at the exportxl macro. I think it can do everything that you described. You can download it from: http://www.sascommunity.org/wiki/Excelling_to_Another_Level_with_SAS   Art, CEO, AnalystFinder.com   ... View more

We're using SAS on Unix OS only but the thing is will that entry works to connect SQL server using windows authentication (Domain\Username)?   Yes, I've put the entry in this format only but when we run the libname we get the below error.   libname test odbc user="XXXXX\XXXXXX" password='XXXXXXXXXXXXXXX' datasrc="test" schema=XXXXXXXXX;   ERROR: CLI error trying to establish connection: [unixODBC][Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed for        user 'XXXXXX'. ERROR: Error in the LIBNAME statement.   Could you confirm if the same entry format works for windows authentication? ... View more

You have plenty of good suggestions that work for what you have presented.   However, suppose your data set contains additional variables and you would like to preserve some values of those other variables?   Here's a solution that best addresses the issue of "additional variables":   data want; update have (obs=0) have; by id category; run; ... View more

Hi everyone, I have got temporary solution to the posted question about memory issue. What I did is to change ddfm =kr in the model statement to ddfm=satterth. I also put all my ods output statement outside proc mixed and not within proc mixed procedure. I used as well ods noresults. ... View more

@Cindarellie wrote: Hello! I'm trying to create a variable that just pools all of the participants responses into one variable.   For example, there was a question that ask which following fruits do you eat? The participants can check off whether or not they eat each option, where 1=they checked it. So I want to create a variable where all the yes responses are in just one if that make senses.   When I run this code, I don't get any errors and the variable is created, however I noticed through PROC FREQ the frequency doesn't match the original variables-so I am wondering how to make sure it is pulling things correctly or what is happening for it to be getting the wrong number of observations?   I am not sure creating the variable using the if function is possible as that is most familiar method I use to create new variables. I am not familiar with arrays but would would that be better?        if q_apple=1 then fruits="apple"; else if q_orange=1 then fruits="orange"; else if q_banana=1 then fruits="banana"; else if q_grapes=1 then fruits="grapes"; else if q_watermelon=1 then fruits="watermelon"; else if q_strawberries=1 then fruits="strawberries"; else if q_bb=1 then fruits="blueberries"; else if q_ch=1 then fruits="cherries"; else if q_other=1 then fruits="Other"; Show example starting data and what the result should look like. Otherwise there is lots of guessing as to what you want. ... View more

Three things to add to @SASKiwi's suggestion: It is rarely (if ever) necessary to store date or datetime literals in macro variables or parameters. It is easier and simpler to use the raw values. And, if your macro contains macro code (%let, %if or %do), prevent premature execution of such statements with %nrstr. You also seem to look back one year, so I added that. next_date = intnx('MONTH', date, i, 'B'); prev_date = intnx('year',next_date,-1,'s'); YYMM = compress(put(next_date, yymm6.),'M'); call execute(cats('%nrstr(%Dave(',YYMM,',',prev_date,'));')); ... View more

@DaveStar wrote: Your answer is similar to following question: Question:What is the best diet? answer: Not eating     Edit:  What @hashman said - I hadn't seen his answer yet before posting.   A bit of advice:   1) The approach in your original post sucks. 2) It sucks whether you want to believe it or not. 3) Smarter more experienced SAS programmers on this board are trying to help you. 4) Your flippant comment above doesn't help us want to help you.   If your poorly designed data transfer processing really IS macro variables, then here is an approach:   %let m0=1906; %let m1=1905; %let m2=1904; %let m3=1903; %let m4=1902; %let m5=1901; %let m6=1812; data stuff; set sashelp.vmacro; where prxmatch('/M\d+/',name) and scope='GLOBAL'; * danger of grabbing macro variables you don't want ; date=input(cats(value,'01'),yymmdd6.); * uses YEARCUTOFF value ; * or date=input(cats('20',value,'01'),yymmdd8.); * if all years are in this century ; * keep date; format date yymmddn8.; run;   Then deal with your data as it was meant to be transferred to you in the first place. ... View more