@CJJC wrote: Hello all;   I'm still new to SAS and I'm having trouble getting a project to use corrected datasets.   I have six permanent datasets that had coding problems.  One by one, I made code changes in the six projects that provided the correct end results. I have a 7th project that pulls in all of the corrected datasets but the first data step is to merge all of datasets together using a shared variable.   For some reason the older, incorrect datasets are being called in.  Why does this happen?   Maybe because you didn't save the corrected data sets, or you saved them in the wrong location. If that's not it, show us the code to create one of the corrected data sets, and then also show us the code that tries to read it in.     ... View more

UNTESTED CODE   data want; retain household; set have; if hoh=1 then household=id; run; ... View more

@cjpink07 wrote: Yea that's what I have been doing and yes my company wants each (I mean every single) graph lol What are you going to do with all of these plots once you have them? ... View more

That's a lot of plots, around 2,000! What are you going to do with them once you have them? Depending on what you plan to do, we might be able to suggest other methods.   If you really really really really need 2,000 plots, this isn't hard to program. Use PROC SGPLOT with a BY statement. ... View more

data want; set df_a df_b; run; ... View more

I didn't look carefully, did you include example data where we would need to take into account the last date for the patient? ... View more

Are the dates by ID in increasing chronological order? If not, then sort the data by ID and date.   data want; set db1; by id; if first.id then flag=1; else flag=0; run;   I don't understand this part, and it would help if you explain further and include an example in the sample data set.   Moreover, this should be done from the start (first date that appears) to 30 days prior to the end (last date). ... View more

Impossible to read this table. Make a screen capture and then click on the "Insert Photos" icon here and include it in your reply. Also show us the PROC FREQ code used. Please also show us the code (as text) and the output (as a screen capture) from PROC LOGISTIC. ... View more

You are now confusing the SUM function with the SUM statement. These are not the same. The SUM function does require a RETAIN, again as clearly stated at the link from @FreelanceReinh which you should really look at. The SUM statement does not require a RETAIN, as clearly stated at the link. ... View more

@Ronein wrote:  so the rule is that SUM statement doesn't have built in Retain whereas plus have built in retain?  You are making stuff up. No one said that. There is no "plus" statement, it is the SUM statement, you are using the SUM statement. Please click on the link from @FreelanceReinh and see for yourself. ... View more

If you had clicked on the link provided by @FreelanceReinh you would see that the Sum statement is exactly what you are talking about. ... View more

I'm going to insist that we stop here. I'm going to insist that in your first post in a thread, you describe the problem from the beginning all the way to the end, in words, without referring to SAS code at all. Then you need to show us (a portion of) the original data (not the data transformed or transposed after a couple of steps) and show us the desired output. This is the proper way to ask for help and will lead to the most efficient discussions, by providing these items I just described. This is the only way for us to make progress efficiently. You need to provide this for EVERY problem you want us to help with. No jumping into the middle and asking how to rename variable names; no jumping into the middle and wondering why your PROC REPORT has an error. ... View more

Maxim 14 — Use the right tool   PROC REPORT is not the right tool for this type of output. Maybe PROC TABULATE will work, but I have almost no knowledge of PROC TABULATE. So maybe @ballardw can step in and show how (if possible) you can get this from PROC TABULATE. I suspect he will need to see a portion of your original (untransposed) data.   PROC REPORT produces rectangular tables where a variable (for example, YEAR) is going across the top and another variable (such as income catergories) goes down the first column. I'm guessing you could probably work very hard and make this table in PROC REPORT but I do not even want to think about working very hard to do this.   If somewhere earlier in your code for this project, you wrote code to create the age category '20-24' in a variable AGE1, and similarly for sex and race, this is also counterproductive and makes more work than the much better method, which is to assign a custom format to the original variable. Then in reporting procedures, SAS is smart enough to be able to know that the values associated with '<20' come before the values associated with '20-24' and then put them in the proper order in the desired table, without you having to force an ordering. The reason we started with a seq variable was because it seemed as if you wanted possibly values in a table that were not in alphabetical order or not in numeric order. ... View more

Why are you transposing? It doesn't seem necessary. Is it to get the columns in a report? Then it certainly is NOT necessary, and in fact it is the wrong thing to do. Show us the report you want — type it in using Excel and show us the screen capture.   Remember, no more transposing to get a report.   Why this:   if sex='Male' then sex1=1; else if sex='Female' then sex1=2;   Why this:   if age='<20' then age1=1; else if age='20-24' then age1=2; else if age='25-29' then age1=3; else if age='30-34' then age1=4; else if age='35-39' then age1=5; else if age='40-44' then age1=6; else if age='45-49' then age1=7; else if age='50+' then age1=8;     Is it to control the order in a report? There are other ways (that are much easier) if things are already in order. Your ages are in order. Your sexes are in order. The reason I proposed a different approach earlier was you wanted an order that was not alphabetic. ... View more