topic Re: Behavior change from EG4.1 to EG 4.2 in SAS Enterprise Guide

Behavior change from EG4.1 to EG 4.2

nwelke — Thu, 17 Jun 2010 17:21:18 GMT

Hi all,
We've noticed a difference between how EG 4.1 and EG 4.2 generate (or store) session parameters.

EG 4.1 generates this output:

%put &_CLIENTUSERNAME &_CLIENTMACHINE;
nick.welke D03CB4

And EG 4.2 generates this:

%put &_CLIENTUSERNAME &_CLIENTMACHINE;
'nick.welke' 'D03CB4'

Does anyone else get this same result? Is it something we can disable in 4.2 to remove the quotes?

TIA
Nick

Re: Behavior change from EG4.1 to EG 4.2

Technolero — Fri, 18 Jun 2010 12:47:30 GMT

I have noticed the same thing. I had some date macro variables in the titles of my reports that no longer display. I have not spent much time finding a solution, so if anyone has one it would be greatly appreciated!

Re: Behavior change from EG4.1 to EG 4.2

RichardH_sas — Fri, 18 Jun 2010 13:48:11 GMT

Suggestion from SAS Tech Support is:

%sysfunc(compress(&_clientusername,%str(%')))

Nick, you probably received the same message from Tech Support, but I figured I'd post it here for others to look at, Not sure if the EG developers will offer a less programatic workaround in the future.

Re: Behavior change from EG4.1 to EG 4.2

Patrick — Sat, 19 Jun 2010 18:52:56 GMT

Why not using dequote() instead?

%let _CLIENTUSERNAME='nick.welke';
%put %sysfunc(dequote(&_CLIENTUSERNAME));

Re: Behavior change from EG4.1 to EG 4.2

twocanbazza — Sun, 20 Jun 2010 20:30:25 GMT

One would have to ask why the change? you would think code run in previous versions would be able to run with the same results/output successfully in current versions.

Barry Message was edited by: twocanbazza

Re: Behavior change from EG4.1 to EG 4.2

boschy — Fri, 02 Jul 2010 00:17:26 GMT

I dare say that someone complained about problems with unquoted strings. I wonder if the majority of EG users were happy with the old approach.