@aaronsterri wrote: Thanks so much for your kind reply.   for some reason, i get the following error for the yearqtr variable. ERROR 48-59: The format $YYQ was not found or could not be loaded.   any help is really appreciated. have a great night! This is just a matter of paying close attention to the message, vs my suggestion.  In particular, you will not find a format $YYQ used in my code. ... View more

@aaronsterri wrote: Thanks so much for your kind reply.   for some reason, i get the following error for the yearqtr variable. ERROR 48-59: The format $YYQ was not found or could not be loaded.   any help is really appreciated. have a great night! This is just a matter of paying close attention to the message, vs my suggestion.  In particular, you will not find a format $YYQ used in my code. ... View more

@abhityagi wrote: For Example: I have data set    Dataset1: Columns: A B C D E F;   Dataset2: Columns: A B;   Dataset 3: Columns: C D;   Dataset $: Columns: E F;   Here I want to data compare dataset1 with dataset2, 3 and dataset4.     PROC COMPARE will handle this:   data base comp1 (drop=name age) comp2 (drop=age sex) comp3 (drop=height weight) comp4 (drop=age sex weight) ; set sashelp.class; run; %macro comp(base=,comp=); proc compare base=&base comp=∁ run; %mend; %comp(base=base,comp=comp1); %comp(base=base,comp=comp2); %comp(base=base,comp=comp3); %comp(base=base,comp=comp4); If this does not summarize your data requirements please provide more explanation.  Otherwise why reinvent the wheel? ... View more

At this point, the answers have been given to the question asked; but I think the real question that needs an answer is why do you want to resolve a macro variable in single quotes in the first place? This seems like a misunderstanding and could have been easily solved if only you told us what the real goal of the program and explained where you are and where you want to go, rather than you want to resolve a macro in single quotes. ... View more

Thanks a lot. It is good to know we have to add Start-Process before call sas.exe   Did anyone try call SAS EG Project from PowerShell?  I tried, but it only pops up EG window, not execute the Project Flow, wondering what is the trick(or option) I have to give here?   Lynn   ... View more

Since a change in the spreadsheet might easily cause a change in the structure of the dataset, updates cannot be done (simply) in a reliable way. You can only rewrite the dataset and try to live with the unpredictable results. To make such a process sustainable and reliable, you need to cut Excel out of your data processing chain. ... View more

@Jumboshrimps wrote: Again, thank you.   Are you referring to: "%let return=&target..&memname;"?   Would that line return the name of the just unpacked dataset in the temp SAS WORK  directory to the  calling SET statement from the original program?   I incorporated the %sysexec changes, and all is good.   NO.  That is macro statement that is setting the value of a macro variable named RETURN. It will not emit any code that will be passed onto SAS to execute. If you look later in that macro you will that it also includes this line: &return That is evaluating the value of the RETURN macro. And since it is NOT part of any macro language statement the value will be sent be the macro processor onto SAS to evaluate.  So that is the place where the name of the dataset to use the SET statement (or where ever you are calling the macro) is being sent from the macro back to SAS. ... View more

Thank you ... 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