I just received a reply from TS and they suggested the following two options to fix the issue: 1) Use outputwidth=100% option in the ODS TEXT statement; 2) Modify the style being used so that the the outputwidth of the ODS TEXT element (usertext in the style definition) is 100%. 1) Would be as follows: ODS ESCAPECHAR="^"; ODS RTF STYLE=JOURNAL BODYTITLE FILE="TEST.RTF"; ODS RTF STARTPAGE=NEVER; ODS RTF TEXT="^S={outputwidth=100% preimage='C:\SAS_TPTK_logo.jpg'} "; ODS RTF TEXT="Second line"; PROC PRINT DATA=SASHELP.CLASS; RUN; ODS RTF CLOSE; 2) Would be as follows: ods path work.template(update) sashelp.tmplmst; proc template; define style styles.myjournal;   parent=styles.journal;   style usertext from usertext / just=c outputwidth=100%;   end; run; Thank you very much to Bari from TS for the quick reply and the two solutions to this problem! ... View more

Hello Cynthia and data_null_, First, I confirm that data_null_'s workaround also works in SAS 9.3 under Windows. Here is the reply I got from TS, with another way to work around the problem: The problem that you are encountering is actually a defect in ODS PDF where the unicode function is causing double spacing.  It is explained a little further in this note http://support.sas.com/kb/33783. I was able to get the correct alignment with the following workaround: "Difference (^S={font_size=5pt}^{UNICODE 0394}^S={}) adjusted~geometric mean percent change (95% CI)"; Thank you both and thank you to SAS TS for all your helpful replies Daniel ... View more

Hi:   You are talking about the fundamental differences between a PDF file (in which every page is considered to be a separate table and UNIFORM makes sure that every page's table is treated the same way.) In RTF, on the other hand, the RTF specification says that a table can span multiple pages. It doesn't matter whether the table takes up 1 page or multiple pages. Of course if the table DID take up 1 page then you would see the behavior that you want. However, for a table that takes up multiple pages, the footer will appear on the last page. (COMPUTE BEFORE _PAGE_ works the way you want for RTF).   In order to mimic what PDF does (treat every page as having a separate table) most folks make a "dummy" or "fake" page break variable and instead of doing COMPUTE AFTER _PAGE_, you would do a COMPUTE AFTER FAKEVAR; block that would put your footer. This does mean a bit of testing to be sure that you set the right number of obs for every group. See the code sample below. cynthia ** make a "fakevar" for page breaking; ** may have to test the number used here; ** I picked 30 but probably could have used 31 or 32; data demo_alt;   set sashelp.demographics;   fakevar = ceil(divide(_n_,30)); run;             ods listing; proc print data=demo_alt; var fakevar region name pop; run;            options orientation=portrait; ods listing close; ODS RTF  FILE="c:\temp\TEST.RTF"; ODS PDF FILE="c:\temp\TEST.PDF" UNIFORM;            PROC REPORT DATA=demo_alt NOWD;      COLUMNS fakevar REGION NAME POP;      define fakevar / order noprint;      DEFINE REGION / order;      COMPUTE BEFORE _PAGE_;         LINE "This is my table title";      ENDCOMP;      break after fakevar / page;      COMPUTE AFTER fakevar;         LINE "This is my table footer value of fakevar=" fakevar;      ENDCOMP; RUN;        ODS _ALL_ CLOSE; ... View more