| Date: | Wed, 21 Mar 2012 12:56:47 -0400 |
| Reply-To: | Arthur Tabachneck <art297@ROGERS.COM> |
| Sender: | "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> |
| From: | Arthur Tabachneck <art297@ROGERS.COM> |
| Subject: | Re: Why is the following result dependent upon NOPRINT |
|
Gabe,
Thanks and, yes, that would definitely work and both &countvar and &sqlobs
could be used that way.
I actually ended up using neither and used proc sql to create macro
variables to accomplish everything I was going to do based on the number of
variables that met the condition.
Fortunately, this morning, I'm drinking more coffee.
Art
---------
On Wed, 21 Mar 2012 11:17:47 -0400, Gabriel Farkas <g.farkas@GMAIL.COM>
wrote:
>Arthur,
>
>If you're looking for a count of the number of variables that met the
>conditions, while still invoking the NOPRINT option, I think the following
>might get you what you want.
>
>
>proc sql
>noprint
>;
> select count(name) into :countvar
> from dictionary.columns
> where libname="WORK" and
> memname="SHEET1" and
> type="char" and
> name ne "isin"
> ;
>quit;
>%put &countvar.;
>
>
>
>Regards,
>Gabe
>
>
>
>On Tue, 20 Mar 2012 12:14:05 -0400, Arthur Tabachneck <art297@ROGERS.COM>
wrote:
>
>>Thanks Tom, Mike and Sai!
>>
>>Sai, As Mike pointed out, the documentation isn't quite correct, as
creating
>>a macro variable also would have produced the expected &sqlobs value.
>>
>>However, I now understand why I didn't get the anticipated outcome.
>>
>>Thanks again,
>>Art
>>-------
>>On Tue, 20 Mar 2012 11:51:44 -0400, Sai Venkat <chsv.1983@GMAIL.COM>
wrote:
>>
>>>%put &SQLOBS
>>>contains the number of rows that were processed by an SQL procedure
>>statement.
>>>For example, the SQLOBS macro variable contains the number of rows that
>>were
>>>formatted and displayed in SAS output by a SELECT statement.
>>>http://support.sas.com/documentation/cdl/en/sqlproc/62086/HTML/default/vi
ew
>>er.
>>>htm#a001360983.htm
|