It looks like you are tying to join the Oracle table OS.CHARGE to the SAS dataset WORK.TEST2.
If OS.CHARGE is large then you will probably need to upload a copy of TEST2 into Oracle in order to prevent SAS from pulling ALL of OS.CHARGE over to SAS.
If you are getting syntax errors then please show the lines from the SAS log. Make sure to paste in the lines of text from the log (not a Polaroid of your screen) using the Insert Code button on the editor so that the formatting is preserved.
... View more
Thank you so much. This worked as well. I am usually just pulling variable using pass through and then joining. this is more efficient and seems faster.
... View more
this is clever! I ran this and found that my data has duplications for DF. But I would want to keep the DF step with the latest sequence number. The other thing is that i got some duplicate outputs in my result for some reason. I will go with the data step solution but thank you for this. i have never thought about joining a table back on itself...
... View more
No, I didn't catch that. However, that could be added as a data step instead of proc tabulate. The important part for this question, IMO, is the design of the program and how it should be structured.
... View more
