Hi Dmorrell, I think use SASHELP to the maximum instead of using these heavy codes. Once you import Excel file into sas then use SASHELP tables namely Dictionary.tables or sashelp.VTable to obtain every information about every element in the datasets present or user created. Thanks ... View more

Here is a published sample that accounts for before and after 2007: Sample 24735: Compute daylight saving time http://support.sas.com/kb/24735 Cheers, Jan ... View more

, FWIW, while your code delivers the top 3 obs, it will still read through the whole 'test' table. It would take a toll on your efficiency if the 'test' is big (billion records in heath care or financial data) or fat (seen 100k variables in some Microarray data) or both . I would recommend the following tweak: data name;   set test;   if _n_>3 then stop; run; Haikuo ... View more

Make sure that the variables from the freekids data set do not also exist on the s1net data set. When we get this question in Tech Support, 90% of the time the answer is extraneous variables on the second data set. If variables on s1net that match variables on freedkids data set and have values, you may need to do a merge and test for missing value.  Here is one possibility: data test1; infile datalines truncover; input id var1 var2; datalines; 1 1 1 2 2 3 3 3 4 4 ; data test2; infile datalines truncover; input id var2 var3; datalines; 1 11 11 2 21 21 3 . 31 4 41 41 5 51 51 ; data result;   merge test1 (in=in1) test2(in=in2 rename=(var2=var22)); if in1 then do;   if  in2 then do;     if var2 = . then var2 = var22;   end; end; else if in2 then var2 = var22; run; proc print data=result; run; Cheers, Jan ... View more

The root of the issue is that macro references are resolved once before the DATA step is compiled. Your code attempts to change the variables referenced by changing the values of the macro variables. This demonstrates the general idea of what I am attempting to describe.  The SAS code runs without syntax errors, but there are no guarantees that it is correct.  I will leave that to your expertise. /* test1.sas */ DATA data; INPUT President $ Party $ X pf1_20 pf1_40 pf1_60; DATALINES; Adams F 2 10 20 30 40 Lincoln R 16 10 20 30 40 Grant R 18 10 20 30 40 Kennedy D 35 10 20 30 40 Adams F 4 10 20 30 40 Lincoln R 17 10 20 30 40 Grant R 22 10 20 30 40 Kennedy D 35 10 20 30 40 Adams F 8 10 20 30 40 Lincoln R 11 10 20 30 40 Grant R 19 10 20 30 40 Kennedy D 40 10 20 30 40 ; RUN; %let startperc1=20; %let endperc1=60; %let stepperc1=20; %let sortingvar1=X; %let nowperc=%eval(&startperc1); %let prevperc=%eval(&startperc1-&nowperc); data newdata;     set data; nowprec = &nowperc; prevperc = &prevperc; array pf1 (*) pf1_0 pf1_20 pf1_40 pf1_60; pf1_0 = 0; pnt = 1;  /* pointer for pf1 array */ do while (nowperc lt &endperc1);    if &sortingvar1>=pf1(pnt) AND &sortingvar1<pf1(pnt + 1) then      rank = (nowperc - &startperc1 ) / ( &stepperc1 +1);       nowperc + &stepperc1;    prevperc + &stepperc1;    pnt + 1; end; drop pnt pf1_0; run; Cheers, Jan ... View more

thanks all for your comment... ... View more

Start a new thread and clarify your questions please. ... View more

AllSoEasy: I don't think you got the message.  You didn't have an apostrophe in the comment you showed and, if if you did, the /*  */ type of comment would not have been bothered by it. You likely have a different problem, like an embedded apostrophe in one of the other not recommended (for a macro) comment types, or an incomplete set of /* */ comments. I would suggest changing all of your comments to the /*  */ type, leave the questioned comment in your code and make sure that the code runs.  Otherwise, you risk the possibility that an essential line of code is being ignored. ... View more

, I added the new WORK location to MS essentials, and till now no more such kind of errors. It seems like a MS essential authorization related issue. Thanks for the suggestion! ... View more