| Date: | Wed, 9 Jun 2010 18:19:54 -0400 |
| Reply-To: | Randy Herbison <RandyHerbison@WESTAT.COM> |
| Sender: | "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> |
| From: | Randy Herbison <RandyHerbison@WESTAT.COM> |
| Subject: | Re: Inserting a table in an ODS REGION? |
|
| In-Reply-To: | <AEABC21942B1974B82CB5B3605B8C4520B266F@ofmmxalc712.ofm.wa.lcl> |
| Content-Type: | text/plain; charset="us-ascii" |
Without using a layout, print the largest table, measure it, and see if your region dimensions are realistic.
-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Sprague, Webb (OFM)
Sent: Wednesday, June 09, 2010 3:05 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: Inserting a table in an ODS REGION?
Hmm... I was hoping NOT to use the gridded ods approach (with rows and
columns) but rather the absolute, like:
ods layout start;
ods region x=5.25 y=4.00in width=5.0 height=3.5;
I will keep hacking at it, though, and maybe go back to the gridded.
Thanks!
> -----Original Message-----
> From: Huang, Ya [mailto:Ya.Huang@amylin.com]
> Sent: Wednesday, June 09, 2010 12:02 PM
> To: Sprague, Webb (OFM); SAS-L@LISTSERV.UGA.EDU
> Subject: RE: Re: Inserting a table in an ODS REGION?
>
> Ok, it has something to do with ods layout start statement:
>
> This will give you the message "WARNING: The absolute region was too
> small to accommodate the text supplied. OUTPUT WAS LOST."
>
> ods listing close;
> ods pdf file="c:\temp\junk.pdf";
> ods layout start;* rows=3 columns=2;
>
> ods region row=1 column_span=2;
> proc print data=sashelp.class (obs=2);
> run;
>
> ods layout end;
> ods pdf close;
>
> If you uncomment the "row=2 columns=2" from ods layout start
statement,
> it will
> work fine. So, it seems that we can't ignore those options for ods
> layout start statement.
>
>
> -----Original Message-----
> From: Sprague, Webb (OFM) [mailto:Webb.Sprague@ofm.wa.gov]
> Sent: Wednesday, June 09, 2010 11:06 AM
> To: Huang, Ya; SAS-L@LISTSERV.UGA.EDU
> Subject: RE: Re: Inserting a table in an ODS REGION?
>
> Replies below ...
>
> > Most likely your proc print has too many lines that won't fit in the
> > region. Try proc print data=xx (obs=5), see if it fit in this time.
> > Also, you can reduce the size of the image, which may take too much
> > space. If you really need to squeeze in all of them, you need to
> > reduce the font size for proc print.
>
> I tried (obs=3), still have the same problem.
>
> Tried style with a fontsize of 5pt, same problem.
>
> There is no way to reduce the size of an image for the table (though I
> tried it anyway).
>
> How does one even know how to proceed with this? Is there a way to
> find
> out how large the table being produced is, so that I can tweak it
> without being in the dark?
>
> Thanks to all for the help!
|