I understand. In that case, it's better to go with what @PaigeMiller suggested. Would you like help with that or do understand what he was suggesting?
However, save the colon wildcard in the back of your mind somewhere. It is a useful technique. If you prefix all your work variables with an underscore, you can code a single drop statement such that no work variables wind up in your Production data. For example:
DATA Prod.Very_Important_Data;
DROP _:;
SET Input.Source_Data;
_Daily_Amount = Annual_Amount / 365;
_Standardized_Quarter = (30 * 3);
Quarterly_Amount = _Daily_Amount * _Standardized_Quarter;
RUN;
The above example is a bit contrived, but in this case _Daily_Amount and _Standardized_Quarter are removed from the final results because of the Drop statement. In a program with dozens of intermediate or work variables, the colon modifier is very handy.
Jim
... View more