You now have around 15 posts from the last day or two open on the same set of subjects. If you are struggling in your job to do something, I would suggest going on a course or something like that, or hire a contractor to the work for you. Repeatedly posting the same questions over and over, ignoring the suggestions provided will not get you any further to your goal.
YOU are the only one who has access to your data and knows what it looks like, combines together. Therefore YOU are the only person who can create a proper data model of how data will join/link, model up into how you know the output should look like.
I will repeat what I have said before, draw out on a bit of paper your data model, that is all the datasets you have, and then draw lines between each one to see how those datasets link together. Once you have an understanding of the whole model, then you can add the various joins together and processing. This also documents the process. Just "adding in some proc code", or "combining other bits of code" will lead to frustration, and will most likely not get you the end product you desire anyway.
Why do you want to combine so many things? Keeping code in short steps makes it easier to read.
You now have around 15 posts from the last day or two open on the same set of subjects. If you are struggling in your job to do something, I would suggest going on a course or something like that, or hire a contractor to the work for you. Repeatedly posting the same questions over and over, ignoring the suggestions provided will not get you any further to your goal.
YOU are the only one who has access to your data and knows what it looks like, combines together. Therefore YOU are the only person who can create a proper data model of how data will join/link, model up into how you know the output should look like.
I will repeat what I have said before, draw out on a bit of paper your data model, that is all the datasets you have, and then draw lines between each one to see how those datasets link together. Once you have an understanding of the whole model, then you can add the various joins together and processing. This also documents the process. Just "adding in some proc code", or "combining other bits of code" will lead to frustration, and will most likely not get you the end product you desire anyway.
Concur with others: don't.
Unless you belong to the people who like to run head-first into concrete walls, so that they can complain about the headaches.
And strongly concur with @RW9. Get to know your data (Maxim 3), or model it intelligently (Maxim 33, Maxim 19 and Maxim 49), make a plan (Maxim 43 and Maxim 16), define steps (Maxim 34), use the right tools (Maxim 14), test frequently (Maxim 4 and Maxim 36).
With Maxim 13 in mind, you might reap the fruits of Maxim 41.
Unless you belong to the people who like to run head-first into concrete walls, so that they can complain about the headaches.
Its called parkour.
@RW9 wrote:
Unless you belong to the people who like to run head-first into concrete walls, so that they can complain about the headaches.
Its called parkour.
Don't they try to hit the wall feet-first?
😉
At least the guy who ran away from James Bond did.
Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.