This is a root-finding problem. Define f(lambda) = target - cdf("poisson", n, lambda); and solve for the zeros of f. This is always possible (and has a unique solution) because the CDF is an increasing function of lambda. (Of course, 0<target<1). To solve the problem, find a root-finding algorithm such as the bisection method implemented in SAS. (I believe that the %inv macro at http://ftp.sas.com/samples/A57496 gives you what you need; Although it is written as a macro, you ought to be able to decipher it.) If you have SAS/IML, see http://support.sas.com/documentation/cdl/en/imlug/63541/HTML/default/viewer.htm#imlug_genstatexpls_sect004.htm ... View more

Hi: I can think of 2 methods: 1) Left-justify the default for ALL headers, including the spanning header, in the PROC REPORT statement and then in the DEFINE statement, change the ones you do NOT want left justified; 2) use COMPUTE BEFORE _PAGE_ with a style override for the justification -- this will span ALL the columns in the column statement -- not just 2 columns, however. cynthia [pre] ods listing close; ods rtf file='c:\temp\usestyle1.rtf'; title "1) Justify ALL the Headers Left and then change the ones you do NOT want left-just"; proc report data=sashelp.class nowd style(header)={just=l}; column ('BaseLine Results' age name) height weight; define age / order style(header)={cellwidth=1.25in} 'Laboratory Test'; define name / display style(header)={cellwidth=1.25in} 'The Name'; define height / display style(header)={just=c cellwidth=1.25in}; define weight / display style(header)={just=c cellwidth=1.25in}; run; ods _all_ close; ods rtf file='c:\temp\usecompute2.rtf'; title "2) Use COMPUTE BEFORE"; proc report data=sashelp.class nowd style(header)={just=l}; column age name height weight; define age / order style(header)={cellwidth=1.25in} 'Laboratory Test'; define name / display style(header)={cellwidth=1.25in} 'The Name'; define height / display style(header)={just=c cellwidth=1.25in}; define weight / display style(header)={just=c cellwidth=1.25in}; compute before _page_/ style=Header{just=l}; line 'BaseLine Results'; endcomp; run; ods _all_ close; [/pre] ... View more

Thanks! ... View more

Thanks, Dan. This is really helpful! ... View more

Again, thank you! Good information. ... View more

Thanks for the information! For the folks at SAS, could I suggest that this definition be placed in the documentation in an easier place to find? The page covering CV (http://support.sas.com/documentation/cdl/en/statug/63033/HTML/default/statug_ttest_a0000000123.htm) has a section for the lognormal distribution, but does not mention that it is calculated differently from the normal distribution, which would tend to lead people to believe it is calculated the same way. Thanks! Message was edited by: Kastchei ... View more

Thanks Dan for the tips. I was skeptical about the min and max, because the documentation says this only works with linear and time axes. However, specifying max = 25000 did indeed produce LOG-LINEAR plots where the log axes had a maximum of 25000 for each plot. Thanks! ... View more

Have you looked at proc means ? ... View more

The HTML seems to have wreaked a little bit of havoc on an otherwise very illuminating and much appreciated answer 🙂 thanks ... View more

Hi: With the BREAK statement (to be used with an ORDER or GROUP item), you can use the PAGE option. That will ensure that every group starts on its own page. For example, see the program below. There may be times when you need to set a dummy variable for page breaking. I find I usually need to do that when there's some arbitrary order or page breaking that I want to impose on a report. If you want to get the page breaking without the summary line, you'd could use this BREAK statement: [pre] BREAK AFTER REGION / PAGE;[/pre] cynthia options nodate number orientation=portrait; ods listing close; ods pdf file='c:\temp\Asia_Canada.pdf'; proc report data=sashelp.shoes nowd; where region in ('Asia', 'Canada'); column region product subsidiary sales; define region / group; define product / group; define subsidiary / order; define sales /sum; break after region / summarize page; run; ods pdf close; ... View more

Somehow you are getting the SAS ODS option NEWFILE=PROC associated with your SAS execution. On the ODS statement, try coding NEWFILE=NONE to suppress/override the behavior. Scott Barry SBBWorks, Inc. ... View more

Yes, the breaks are strictly there to force white space between groups. The just works fine with one break statement, but not with both. Thanks for the advice. I'll put in a ticket. ... View more

Hi: There are either ODS ESCAPECHAR methods (padding the front of a variable with non-breaking space) or style attribute methods -- using INDENT= or LEFTMARGIN= attributes. PDF is not a "markup" language like RTF or HTML -- so there's no Adobe-specific set of known "markup" that can be inserted into a PDF file. For information about using style attributes with PROC REPORT, PROC PRINT or PROC TABULATE, consult those procedures' documentation. For information about using style attributes with other procedures, consult the PROC TEMPLATE documentation. For information about ODS ESCAPECHAR in SAS 9.1.3 and a preview of the changes in syntax due in SAS 9.2, see my paper: http://www2.sas.com/proceedings/forum2007/099-2007.pdf or these other papers: http://www2.sas.com/proceedings/sugi29/084-29.pdf http://www.nesug.org/proceedings/nesug07/cc/cc18.pdf http://www2.sas.com/proceedings/forum2007/144-2007.pdf http://www.lexjansen.com/pnwsug/2007/Pete%20Lund%20-%20PDF%20Can%20be%20Pretty%20Darn%20Fancy.pdf cynthia ... View more

In 9.2 there is the capability of aligning columns based on their data type. There is a table template called Base.Template.Table that all table templates inherit from. If you define that table template as follows, it should do what you want. proc template; define table base.template.table; cellstyle _datatype_ = 'num' as {just=d}; end; run; This doesn't apply to Proc Tabulate, Proc Report, or Proc Print though because they do not use table templates. ... View more

Thanks for all the advice. I tried JAVA and JAVAIMG, but both these had the same issue as ACTIVEX with removing the titles plus other unwanted changes. I did try SASPRTC like the articles mention. It works fine, though the graphs are not a pretty as with ACTIVEX. I think once I embed more fonts for SASPRTC to use, it'll be the best solution. ... View more