Actually, it does create a minor problem, well, more of an annoyance than a problem.
I've created prompt in EG 4.3 which asks user for password to connect to an Oracle database. If that password contains % (e.g. A%BCDE), then EG produces warning when the program is starting and macro variables are being assigned:
%LET pass_PASSWORD = XXXXX;
options nosource;
WARNING: Apparent invocation of macro BCDE not resolved.
Similar warning will happen if password contains &.
It doesn't affect the program itself (you can always quote this variable after prompting), but still warnings are annoying.
There's a way to avoid them, typing into the prompt %nrstr(password) instead of password, but it's not humane for the user, is it?
So, to have back the quoting option for prompts (and not %str() as in EG 4.1, but %nrstr(), because it's just % and & who causes "problems", not other special symbols) would be a good idea.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.