Looks like double quotes outside of the single works "LOWE'S" ... View more

This solution is not practical for simple queries where just want to know if there are results.  Overall, SAS EG 8.3 is not an improvement over the old version.  Pretty disappointed overall.   ... View more

We are a little late to the party, but thank you for saving me time looking. 🙂   ... View more

Yes it is added to all code. ... View more

No. Every time I run the code it requires new input.  Just that the input seems to work after the session is open for a certain amount of time for the numeric prompt to be recognized.  I am not having that issue with the text prompts. I just added a new variable with a "text"  year.  That works fine.  Not the best answer but it will do.  I do not know why the numeric year was so glitchy. ... View more

The user needs to enter a year or years - 2019 through 2021.    PROC SQL; CREATE TABLE WORK.DATA_BY_YEAR AS SELECT t1.ORGGROUP, t1.ACCOUNT_ID, t1.ACTIVE_FLAG, t1.ORG_NAME, t1.YEAR, t1.GOAL_TYPE, t1.ABC_PL, t1.DOLLARS FROM SASDATA.CUST_PROFILE_CMB_DATA t1 WHERE YEAR=&YEAR.; QUIT;   I added the . after the macro name and this time it worked.   but so did this code....If I shut down this project and re-open, I will get errors - like it needs time to connect  or something.  Weird.       ... View more

These are the prompts I created using the Prompt Manager.   The first three are text and the last two are numeric.  I am using the prompt input in my code below. WHERE ORG_NAME="&ORG_NAME" and YEAR=&YEAR_19_21; ORG_NAME gives the correct output using the prompt input.  Year, or year_19_21 does not.  I also created a prompt called YEAR.  I copied this from another example, so yes my syntax could be wrong.  The code does work for text. I do not see any examples for a numeric prompt so there must be a difference that I am not aware of.     ... View more

Thank you for the tips! I like the SAS code version and do not need to necessarily add any fields in this step. This takes a while to test but I will respond later today. ... View more

In addition - one file has unique combinations of the joining fields, the other does not and that is why the file ends  up being so large.  We want those multiple joins to split credit so that is actually ok in this scenario. ... View more

I did not sort either data set before the SQL step.  One file is around 152 million and the other is around 12 million I could do a sort beforehand if that would help.  It already runs so long I did not think sorting would help but I can give that a try? ... View more