Date: Wed, 25 Apr 2007 02:47:06 GMT
Reply-To: Theorbo <reply@TO-GROUP.NFO>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Theorbo <reply@TO-GROUP.NFO>
Subject: Re: help with macro processing & dataset creation
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
sorry to respond to my own post, but I found this good reference (in case
others have similar questions) ...
http://listserv.uga.edu/cgi-bin/wa?A2=ind9602c&L=sas-l&D=0&P=23738 - it
explains what you were getting at about the difference with macros between
compile & run time.
"Theorbo" <firstname.lastname@example.org> wrote in message
> Ok ... thanks. The '%' before the IF _is_ a typo (I think). I'll be the
> first to admit that I'm only starting to learn SAS and really don't
> understand why sometimes we use the '%' and don't at other times. I
> thought I read that you always need the '%' before IF/THEN/ELSE logic
> within a macro.
> Again, thanks for your time.
> "Richard A. DeVenezia" <email@example.com> wrote in message
>> Theorbo wrote:
>>> thanks for the suggestions. can you explain why you would do it your
>>> way instead of a macro? I'm wondering how I will modify your code to
>>> make use of my style sheets in ods xml ...
>> I had a terrible time trying to make sense of your original problem
>> statement, perhaps a portion of it was explained in that past week dialog
>> you mentioned. The most effective sample code is created when a working
>> example of the data of a problem is posted.
>> I saw variables such as idlevel<n> and a
>> %IF idlevel1 IN (&pub_id_1 &pub_id_2 <...>) ;
>> which is pretty nasty mismash between macro and datastep. If not a typo,
>> indicates a misunderstanding of scope and timing of macro, compilation
>> and run time.
>> Maybe I have seen too many future forums, but my understanding is that
>> ExcelXP tagset has an option to create a worksheet for each by group --
>> which would definitely eliminate some of the urge to macro.
>> Richard A. DeVenezia