The other thing you might try to do is play with PROC TABULATE and see whether that gives you the kind of order to the statistics that you want. Something like what's shown below. cynthia [pre] proc tabulate data=sashelp.prdsale; where product in ("BED","CHAIR"); class region product; table (region all)*(colpctn n pctn rowpctn ), (all product); run; [/pre] ... View more

Hi: You truly have a problem to report to Tech Support. BOLD on a TITLE statement has NOTHING to do with PROC REPORT. The TITLE statement lives outside of any given procedure and is a global statement. The only place where BOLD would NOT work would be the LISTING or OUTPUT window. There are a few guesses I would make IF your destination is PDF, RTF or HTML and the BOLD option is not working -- somehow your style template (which has BOLD turned on for the SAS System TITLE) is not being applied OR there's something wrong with your install of SAS OR there's something wrong with your template store. At this point, you have a problem that really needs to have Tech Support open a track in order to follow the problem and resolve the issue. Good luck! cynthia ... View more

Hi: you need to be sure to set the ODS ESCAPECHAR = '~'; statement as shown below: [pre] ods listing close; ods pdf file='stack_col.pdf'; ods escapechar='~'; proc report data=sashelp.class nowd; column name age newvar height; define name /order noprint; define age /display noprint; define newvar / computed; define height /display style(column)={vjust=b}; compute newvar / character length=40; newvar = name||"~n"||put(age,3.0); endcomp; run; ods pdf close; [/pre] This will ONLY work in the PDF file that's created. You will see the ~n in the LISTING output. The ODS Escapechar facillity started working in SAS 8.2 -- if this technique is not working for you -- in the PDF file, your best bet is to contact SAS Technical Support for help. Good luck, cynthia ... View more

Hi: First, you CAN change the graph template that's used for your statistical graph. These are the steps you need to follow: 1) understand WHAT graph template is used for your procedure and graph of interest (use ODS TRACE ON/OFF to determine WHAT graph template is being used for your procedure of interest. 2) investigate HOW your graph template of interest is creating its graph area and titles and legends 3) make a copy of of your graph template or otherwise use graph template language syntax to create a changed template 4) possibly change the STYLE template that you're using if you want to change some of the style attributes used in the production of your output (this step can be optional) -- however, your graph template may use style attributes from the style template -- so you may still have to look at the style template before you're all done. You can find some information about Graph Templates, in these papers: http://support.sas.com/rnd/datavisualization/papers/sugi30/GraphStyles.pdf http://support.sas.com/rnd/datavisualization/papers/sugi30/GTL.pdf http://www2.sas.com/proceedings/sugi29/204-29.pdf http://www.mwsug.org/Conference/2005/Statistics/SS400.pdf Otherwise, Tech Support might be your best bet for help with this request. The code involved could be lengthy and several iterations of the program might be required to achieve everything you want. For information on how to contact Tech Support, refer to: http://support.sas.com/techsup/contact/index.html Good luck, cynthia ... View more

So sorry, my bad. By default, the variable created in a compute block is assumed to be numeric. You need to tell the compute block that it is a character variable. I was typing too fast.[pre] proc report data=sashelp.class nowd; .... more code ....; compute newvar / character length=40; newvar = name||"~n"||put(age,3.0); endcomp; run; [/pre] cynthia ... View more

Hi: There's good news and bad news about what you want to do. The good news is that ODS Tagsets.ExcelXP automatically creates multiple worksheet workbooks in Excel. The bad news is that by Microsoft design/specification Spreadsheet ML (Excel XML) does NOT support graphs. If you try to create graphs in an ExcelXP output file, you get this message in the log: [pre] Excel XML does not support output from Proc:Gchart Output will not be created. [/pre] There -is- still good news. If you use ODS HTML or ODS MSOFFICE2K, you can create multiple, separate HTML files, each with a graph on/in it. Then, using a different approach, you can LINK the files together. Microsoft will allow each separate HTML file to be a worksheet, however, ALL the files have to live in a subdirectory. So let's say that you want to call your workbook BigRept.html and it will be stored in c:\temp: c:\temp\BigRept.html you will need a subdirectory called: c:\temp\BigRept_files in the BigRept_files directory, you will have your ODS HTML files AND the graph images files and maybe a CSS file. Let's say the files are stored like this: c:\temp\BigRept_files\chart1.html c:\temp\BigRept_files\chart2.html c:\temp\BigRept_files\chart3.html Then, you also need an "organizing" file...let's call that file orglist.xml and it, too is in the subdirectory: c:\temp\BigRept_files\orglist.xml and it looks like this: [pre] <xml xmlns:o="urn:schemas-microsoft-com:office:office"> <o:MainFile href="BigRept.html"/> <o:File href="chart1.html"/> <o:File href="chart2.html"/> <o:File href="chart3.html"/> <o:File href="Orglist.xml"/> </xml>[/pre] Now, back to your "top" file c:\temp\BigRept.html (or you could call it BigRept.xls), it has to contain ALL the related file names (like those shown in Orglist.xml), but in a different format:[pre] xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40"> [/pre] Now, if you call this file BigRept.xls and IF you have your subdirectory created and place all the related file in the subdirectory, then when you double click on BigRept.xls, then Excel should open all the related files together. If you call the file BigRept.html, then you have to Right Mouse click and either do an Open with Excel or you have to open Excel and manually open the HTML file. Either way, you will get a multi sheet workbook -including- graphics. This approach is outined in this R&D presentation: http://support.sas.com/rnd/base/topics/excel/multisheet_excel_post.ppt So, the good news is that you can do what you want, it just takes a bit more work than using Spreadsheet Markup Language. cynthia ... View more

Hi: I'm not exactly sure what is wanted. Here's some code that stacks name and age from SASHELP.CLASS in one cell, using PROC REPORT: [pre] ods listing close; ods pdf file='stack_col.pdf'; ods escapechar='~'; proc report data=newclass nowd; column name age newvar height; define name /order noprint; define age /display noprint; define newvar / computed; define height /display style(column)={vjust=b}; compute newvar; newvar = name||"~n"||put(age,3.0); endcomp; run; ods pdf close;[/pre] Note how the concatenated variable is built inside the PROC REPORT syntax with a COMPUTE block. You could have done this concatenation in a data step before the PROC REPORT step -- but the COMPUTE block works very nicely. The only thing you have to be careful about is that the variables that you will concatenate together must appear in the COLUMN statement before the computed variable. In order for this to work, you also must use ODS ESCAPECHAR (in this case, a tilde (~) so that you can put a "line break" in between the two variables. What is at the bottom of your note is HTML, which is why I'm confused about what it is you want. When you say that you want to use PROC TEMPLATE instead of the DATA _NULL_ , I'm not sure if you want PROC TEMPLATE for a table template associated with a procedure (like PROC MEANS). A style template won't do what you want and a tagset template might allow you to stack variables in a cell or change HTML or other MARKUP, but PDF is not a markup destination. Yes, it is possible to stack columns inside a TABLE template associated with a procedure. In that instance, you would change the TABLE template, put the TABLE template in an item store like SASUSER.TEMPLAT. Then the next time you use the procedure, if your ODS PATH is pointing to the item store, the procedure would use the changed TABLE template. It seems to me that PROC REPORT will do what you want. cynthia ... View more

I think that NEWFILE= did not work for PDF in SAS 8.2 -- but, the general approach that Olivier outlined should still work for you. If you have a variable that identifies which file your information came from, then you could treat that variable as the "BY" variable. The macro program would be something like what is shown below. It would have to be adjusted for your variables and data values. cynthia [pre] *** the code; %macro doby(byval=xxxxx); ods pdf file="&byval..pdf"; proc print data=big_dsn; where dsnvar = "&byval"; run; ods pdf close; %mend doby; %doby(byval=Asia); %doby(byval=Pacific); %doby(byval=Canada);[/pre] ... View more

Hi: Back on my computer. Here's my example of a style template that works with ExcelXP -- This might be one place to start to experiment with your needed changes. cynthia [pre] proc template; define style styles.mymin; parent = styles.Statistical; replace Body from Body/ background=_undef_; replace table from Output / background=_undef_ foreground=_undef_ borderwidth=_undef_ font_size=10pt; replace Header from Header / background=_undef_ foreground=_undef_ borderwidth=_undef_ font_size=10pt; replace RowHeader from RowHeader / background=_undef_ foreground=_undef_ borderwidth=_undef_ font_size=10pt; replace Data from Data / background=_undef_ foreground=_undef_ borderwidth=_undef_ font_size=10pt; end; run; ods tagsets.excelxp file='c:\temp\use_style.xls' style=styles.mymin; proc print data=sashelp.class; run; ods tagsets.excelxp close; [/pre] ... View more

According to the Doc, it says that FILEVAR doesn't work with the FILE PRINT ODS statement: These arguments affect only listing output: FOOTNOTES and NOFOOTNOTES LINESIZE PAGESIZE TITLE and NOTITLES Do not use these arguments: DELIMITER= DSD _FILE_= FILEVAR= HEADER= PAD In a SAS Macro program, you could loop through a list of files, however and either do a PROC PRINT or a FILE PRINT ODS for each one, sending it to the PDF destination. cynthia ... View more

Hi: I tried this using ODS HTML in SAS 9.1.3 and the 400px did work for me. If you need a quick resolution to this issue, Tech Support may be your best bet. cynthia [pre] ods html file='c:\temp\cw.html'; proc report data=sashelp.class nowd; column name age height; define age /display style(column)={just=center cellwidth=400px}; run; ods html close; [/pre] ... View more

Hi: It is very perplexing. I do not understand how the TITLE statement could possibly be affecting the data table on the report. Perhaps you have OPTIONS NOCENTER someplace in your code??? Your best bet for a quick resolution to this is to contact Tech Support, there must be something else happening in your code that is affecting the data table. PDF does support: options topmargin=1in bottommargin=1in leftmargin=1in rightmargin=1in; It may be possible that the report is centered -starting- at the left margin you gave -- Tech Support can determine whether some combination of options are conflicting with each other. cynthia ... View more

Hi: You may actually need to design a STYLE template that does NOT have a background of white, but instead "undefines" or "turns off" the default background of gray. I do have an example of a STYLE template like this, however, I am not on my machine at the moment. For help with a style template to get rid of the default colors used with Tagsets.ExcelXP, your best bet is to contact Tech Support. cynthia ... View more