I can't read your mind. Please tell us, in words, what is wrong. Also, please show us the code you used that doesn't produce the right results. ... View more

data want; set test1; by usubjid; prev_ae=lag(ae); prev_aendt=lag(aendt); prev_aestdtc=lag(aestdtc); format prev_aendt prev_aestdtc date9.; /* Compare dates of adjacent observations, if they don't overlap then add 1 to JOIN */ if first.usubjid then join=0; if not (aendt<=prev_aendt and aestdtc>=prev_aestdtc) or ae^=prev_ae then join+1; drop prev_:; run;   If you need AESTDTC as character, simply modify my code to so you don't rename AESTDTC (so it leaves AESTDTC unchanged as character) and create a new variable for the numeric SAS date . ... View more

In order to make this work, you cannot have aestdtc as a "character date" and aendt as a numeric date, since SAS does not know how to compare character strings to numbers. Making aestdtc numeric should solve the problem. So this code will create a numeric variable named aestdc, and since both aendt and aestdtc are numeric dates, they can be compared.     data test1; set test(rename=(aestdc=old_aestdc)); aestdc=input(old_aestdc,yymmdd10.); /* the new aestdc in a numeric date */ run;   Now that both are dates, the comparisons should work. This code seems to do what you want.     data want; set test1; prev_ae=lag(ae); prev_aendt=lag(aendt); prev_aestdtc=lag(aestdtc); format prev_aendt prev_aestdtc date9.; /* Compare dates of adjacent observations, if they don't overlap then add 1 to JOIN */ if not (aendt<=prev_aendt and aestdtc>=prev_aestdtc) or ae^=prev_ae then join+1; drop prev_:; run;           ... View more

/* UNTESTED CODE */ data want; set have; retain a1 b1 c1; if not missing(a) then a1=a; if not missing(b) then b1=b; if not missing(c) then c1=c; run;   This code is untested, because we cannot work with data in a screen capture. To get tested code, please provide the data as working SAS data step code (instructions and examples). ... View more

43 set u.amount=(select CEO from updatet1 n where u.timeframe =n.timeframe) _ 73 76 ERROR 73-322: Expecting an =. Use amount, not u.amount ... View more

Please provide the ENTIRE log for this PROC SQL. (We don't want 100s of lines before or after this PROC SQL, just the log for this PROC SQL)   Please copy the log for this PROC SQL as text and paste it as text into the window that appears when you click on the </> icon. DO NOT SKIP THIS STEP. ... View more

The last eigenvalue indicates the collinearity problem. Most of the variability of the intercept and col12 are explained by the last eigenvalue. This probably is cause by col12 being almost all zeros (or all ones), meaning they are highly correlated. In additon, there are other columns with values > 0.7 in the last row, these two other columns indicate most of the variability is in the last eigenvalue, but not as much as col12. ... View more

@wateas wrote: Part of the issue, I think, is the default designation of the reference level.  For the factor "Trt_CC", the reference level being "no_CC" is good, but for "Weed_Rating", the reference level probably shouldn't be 5, because that is the rating for the most weedy plots and is exerting the most influence.  I'll figure out how to set the reference level, and I think I might already have an idea of how to exclude it from the dummy variable.  BRB I disagree completely, reference level has no impact here. ... View more

When you use dummy variables to replace a categorical variable, and there are n levels for this categorical variable, you want to use n-1 dummy variables. So what happens if you re-run the analysis and take col10 and col15 out of this analysis? ... View more

It means your employer or your university needs to renew the license. They probably know about this already. ... View more

Is there a format applied to variable CIG1RP?   What does PROC CONTENTS say for this variable regarding the presence or absence of a format? Please run PROC CONTENTS on the data set used in PROC PHREG and show us the (relevant parts of the) output.   Corrected: Replaced PROC FORMAT with PROC CONTENTS ... 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

Thanks, but I asked you to explain the logic you want to use, this doesn't explain, and doesn't answer my question. (In case its not clear, explain means write words to describe the steps to go from data set 1 to data set 2) ... View more