Dear All,  @Cynthia_sas 's answer is irrelevant to understand the problem, and @Ksharp 's solution is a work around solution, a few steps short to understand the problem. Hat off to both of the SAS experts for your efforts.  Thank your @Coooooo_Lee for discovering this problem.   Apparently, SAS ODS RTF has a coding problem.  It looks like +, -, and = signs are three special characters in this case.  When you have 4 or more these signs alone, SAS will not transcode  them correctly, without a blank space between them and # sign.   (SAS correctly transcode # sign as {\line }, that's correct with RTF specs).   You can use any other characters on the keyboard, or any combination of these 3, you don't need a blank space between them and #.   This defect of SAS coding should not be surprised.  Remember in SAS own macro language, there are a few special characters and you can't use them directly.   SAS wrote two macro functions: %SUBSTR and %QSUBSTR to handle those special cases.     Jianmin Long   ... View more

Hi @COMPAREMISSING , a short answer to your question is YES.  But according to the SAS export @Cynthia_sas , you would not have a SAS solution in any time soon (I can be wrong).    I understand your motivation for this project, and the good news is that the method is out there for quite a long time.  Here is an example for you to start, using a modified program from @Cynthia_sas , and a short description of the method is in a SAS Global Forum 2020 paper.   Good Luck and Happy New Year! title; footnote; ods escapechar='^'; data heart; set sashelp.heart(obs=100); pg=1+floor(_n_/35); data shoes; set sashelp.shoes(obs=150);; pg=1+floor(_n_/35); options pageno=1; ods rtf file='~/sasout/multpages.rtf'; title j=c "SASHELP.HEART" j=r 'Page ^{thispage} of ^{lastpage}' j=l 'PAGE_X_OF_Y'; proc report data=heart; col pg sex status ageatstart diastolic systolic; define pg /order order=internal noprint; break after pg/page; run; title; title j=l 'Page ^{thispage} of ^{lastpage}' j=c "SASHELP.SHOES" j=r 'PAGE_X_OF_Y'; proc report data=shoes; col pg region product sales inventory; define pg /order order=internal noprint; break after pg/page; run; ods _all_ close; title; ... View more

Hi @Tpham ,  The paper you cited is a privative way to answer your request, as @Reeza outlined in this response.   You will also have to figure out a way for a cover page or top page to make the TOC visible, something like this:   this is for a large file with many sections which needs a TOC for each section title/header.  See this file  This is way beyond what SAS ODS RTF REPORT/DOCUMENT is currently doing. Another example for multiple listings/tables with a TOC.   Many Thanks Jianmin Long ... View more

Hi @Ksharp ,  It's a very clever way to handle this request, and your program works nicely for a small dataset, in one page.  The program would not work for a large dataset, ODS tagsets.rtf works better for a large dataset, see the code: proc sort data=sashelp.zipcode out=zipcode(keep=timezone statename countynm city zip); by timezone statename countynm city zip; run; data zipcode; set zipcode; by timezone statename countynm city zip; *if _n_ le 400; if last.city then id=0; else id=1; run; ods tagsets.RTF file="~/sasout/RowRemove.RTF"; options nonumber nodate; proc report data=zipcode spanrows style(header)=[borderbottomcolor=black borderbottomwidth=2px ] style(report)=[ rules=cols] style(Column)=[VJust=C]; columns ID timezone statename countynm city zip; define timezone / group center; define statename / group center; define countynm / group center; define city / group center; define zip / display Center; define ID / display noprint; compute city; if id=0 then call define (_row_,'style','style=[borderbottomcolor=black borderbottomwidth=2px ]'); call define ('Timezone','style','style=[borderbottomcolor=black borderbottomwidth=2px ]'); call define ('statename','style','style=[borderbottomcolor=black borderbottomwidth=2px ]'); call define ('countynm','style','style=[borderbottomcolor=black borderbottomwidth=2px ]'); call define ('city','style','style=[borderbottomcolor=black borderbottomwidth=2px ]'); endcomp; run; ods tagsets.rtf close; but it creates a rtf file that is not a Word document.  That is, if you select a few rows in the column of City, and change the font size to a large number, say 24 points, then you can't read the city name very well, unless you also adjust the cell height, then that will break your table, in terms of pagination.  This is because ODS tagsets.rtf uses an absolute cell height to control the vertical spaces to achieve correct pagination.    By the way, if you run the whole zipcode data, you will have an output of 1100+ pages, there must be a better way to create a zipcode book for about 100 pages.  Think of a dictionary and an alternative for SPANROWS.    Many Thanks Jianmin Long       ... View more

Very impressive @Ksharp , it looks like you can do anything in SAS, but I still have question for your later.  Hi @Reeza , I have seen Arthur L. Carpenter's writings and all he talked about is to do a table with n rows and m columns.   The table @mcook asked was a type of table I learned in the early time of my career, and Microsoft had a solution for that in 1990's.  The idea of a table is that:  a header row followed with a few rows of m columns.  Nowadays from the beginning of SAS tables, we don't really see this type of distinction in SAS tables.   @Ksharp 's solution was really clever, and I haven't seen it in other writings.  In @Ksharp 's previous program, he did it right to make first two rows as header rows, you can see this in Word for table property for row: Repeated as header row at the top of each page.  In @Ksharp 's most recent program, he didn't make Group as a header row, instead he used a page break.    In Word, it's really easy to make as many header rows as you like, but I don't know how SAS handles this one. The Word doesn't use page break, and there are a lot of wrongs about using page break in SAS.  @Ksharp 's program suffers a minor defect, you still can break the code with a minor change in the code:  data Temp1; length Groups SubGroups $ 200; input Groups $ SubGroups $ (nCount Var1 Var2 Var3 Var4 Var5) (?? :best.); datalines; Group1 SubGroup1A-SubGroup1A-SubGroup1A-SubGroup1A-SubGroup1A 27 22.67 9.80 -0.70 0.90 70.73 Group1 SubGroup1B-SubGroup1B-SubGroup1B-SubGroup1B-SubGroup1B 27 23.67 77.27 0.00 0.93 77.70 .... define SubGroups/group style={just=r width=0.5in} style(header)={just=c} ; And other SPANROWS output heavily uses vertical space control methods, the resulting output suffers a lot of defects, and sometimes it is not even a Word document.  For example you can't do any editing, for example make a font larger, and hidden text in a row... Many thanks for @Ksharp 's effort, and let me know it you know how to make Group as a header row.   Jianmin Long ... View more

Hi @Ksharp ,    It's very clever to use the label statement to modify the dataset. I'm still dizzy to get around this concept, but I'll continue to study your code.  It's still a good piece of cake, but one thing you didn't do is that to get the group follows the data.   For example, the Group6 now is on two different pages, can we have Group6 also on the top of page 2?   Many Thanks Jianmin Long ... View more

Hi @Ksharp and @mcook ,    It's a really delicious piece of cake.  I would like to ask @Ksharp for a little bit more difficult table: If I have more data, the table will take a few pages.  What SAS can do to make the Total row on the top of each page, the the group header row also follows the data.  I made a few copies of the data and paste, so the table will have two pages.  See the code, using your program.  The attached file is an example of what I want, and it was created by a SAS macro and data _null_.  data Temp1; length Groups SubGroups $ 20; input Groups $ SubGroups $ (nCount Var1 Var2 Var3 Var4 Var5) (?? :best.); datalines; Group1 SubGroup1A 27 22.67 9.80 -0.70 0.90 70.73 Group1 SubGroup1B 27 23.67 77.27 0.00 0.93 77.70 Group2 SubGroup2A 10 -- -- 0.38 0.93 77.77 Group2 SubGroup2B 10 -- -- -0.89 0.89 9.60 Group2 SubGroup2C 10 79.70 9.77 -0.56 -- -- Group2 SubGroup2D 10 -- -- -0.79 0.99 72.03 Group2 SubGroup2E 14 29.20 70.92 0.00 0.92 70.89 Group3 SubGroup3A 25 23.78 70.59 0.00 0.92 77.06 Group3 SubGroup3B 29 -- -- -0.63 -- -- Group4 SubGroup1A 27 22.67 9.80 -0.70 0.90 70.73 Group4 SubGroup1B 27 23.67 77.27 0.00 0.93 77.70 Group5 SubGroup2A 10 -- -- 0.38 0.93 77.77 Group5 SubGroup2B 10 -- -- -0.89 0.89 9.60 Group5 SubGroup2C 10 79.70 9.77 -0.56 -- -- Group5 SubGroup2D 10 -- -- -0.79 0.99 72.03 Group5 SubGroup2E 14 29.20 70.92 0.00 0.92 70.89 Group6 SubGroup3A 25 23.78 70.59 0.00 0.92 77.06 Group6 SubGroup3B 29 -- -- -0.63 -- -- Group7 SubGroup1A 27 22.67 9.80 -0.70 0.90 70.73 Group7 SubGroup1B 27 23.67 77.27 0.00 0.93 77.70 Group8 SubGroup2A 10 -- -- 0.38 0.93 77.77 Group8 SubGroup2B 10 -- -- -0.89 0.89 9.60 Group8 SubGroup2C 10 79.70 9.77 -0.56 -- -- Group8 SubGroup2D 10 -- -- -0.79 0.99 72.03 Group8 SubGroup2E 14 29.20 70.92 0.00 0.92 70.89 Group9 SubGroup3A 25 23.78 70.59 0.00 0.92 77.06 Group9 SubGroup3B 29 -- -- -0.63 -- -- Group10 SubGroup1A 27 22.67 9.80 -0.70 0.90 70.73 Group10 SubGroup1B 27 23.67 77.27 0.00 0.93 77.70 Group11 SubGroup2A 10 -- -- 0.38 0.93 77.77 Group11 SubGroup2B 10 -- -- -0.89 0.89 9.60 Group12 SubGroup2C 10 79.70 9.77 -0.56 -- -- Group12 SubGroup2D 10 -- -- -0.79 0.99 72.03 Group12 SubGroup2E 14 29.20 70.92 0.00 0.92 70.89 Group13 SubGroup3A 25 23.78 70.59 0.00 0.92 77.06 Group13 SubGroup3B 29 -- -- -0.63 -- -- Total Total 54 45.03 33.00 99.04 43.33 12.01 ; run; proc format; value fmt .='--'; run;; data have; set temp1; if Groups='Total' then Groups=' '||Groups; run; ods rtf file='~/sasout/KsSharp.rtf' style=journal bodytitle; proc report data=have nowd style(header)={background=verylightgray fontstyle=roman fontweight=bold just=c borderbottomcolor=black borderbottomwidth=2} style(report)={rules=cols outputwidth=100% } style(lines)={just=l bordertopcolor=black bordertopwidth=2 borderbottomcolor=black borderbottomwidth=2 background=grayee fontweight=bold}; define groups/group noprint; define SubGroups/group style={just=r } style(header)={just=c} 'Groups'; define nCount/sum style={just=c} format=fmt.; define var1-var5/sum style={just=c} format=fmt.; compute before groups; if strip(Groups)='Total' then len=0; else len=20; line groups $varying20. len; endcomp; run; ods rtf close;   Many Thanks Jianmin   ... View more

Hi @Cynthia_sas and @mcook ,    It looks like @Cynthia_sas has a solution for @mcook 's request, but a simple solution for this one would be something like a change in your code:  pretext='\ql Table1.1 Temp Title\line' The control word \ql will put the title line on the left, while \qr will do the right alignment.  You guess it, \qc will do the center alignment, but that would be default for PRETEXT.  I also took the liberty of adding a line of space between the title line and the table, which is achieved by  the control word \line.  You can have more space by adding more \line, or none by deleting it completely.    Many Thanks Jianmin Long ... View more

Hi @Ksharp , @Cynthia_sas and @ble9245 ,    Here is a link to the %NT macro, it was renamed as %RTF in the publication;  http://ftp.sas.com/techsup/download/observations/obswww13/obswww13.pdf   Thanks.  Jianmin Long ... View more

Hi @Ksharp , @Cynthia_sas and @ble9245 ,    Thanks for @ble9245 's question, even though I don't really understand why would anyone want a listing with only one header on the first page.  This would be the most simple SAS programing for that type of listing/table.   SAS ODS RTF/Proc REPORT goes beyond that.  It would assume one would like to have a table/listing with headers on every page, even though they can put a simple option for your request.   I don't really know if such option exists.  @Cynthia_sas is pretty good at this, and she would have told us such option.    @Ksharp 's solution to use ODS TEXT=' ' was a success story by mistake:  SAS ODS RTF planned a perfect listing/table with headers on every page, by using a control word \trhdr.  But this control word works only in correct environment.  ODS TEXT= was poorly implemented in ODS, after it's done what it was supposed to do, it didn't provide a clean up to reset to the default paragraph property.  ODS RTF TEXT= is the correct one to use, as Cynthia pointed out, by providing a control word \pard and a new empty row.  So, if you compare the results of using ODS TEXT and ODS RTF TEXT, you will see that there is no space between the line by ODS TEXT=' ' and the line of 'Smoking', while there is an empty row between the line by ODS RTF TEXT='' and the line of 'Smoking', plus a control word \pard, which resets to default paragraph property, by Microsoft RTF specification.    If I have to write some SAS programing for this listing, it would be something like this one:  data _null_; set sashelp.heart(obs=90) end=eof; file '~/Smoke.rtf'; if _n_=1 then do; %nt(0, w=6.5, o=p); &b_header; %nt(1, w=6.5); put &br "Page: \chpgn of {\field{\*\fldinst NUMPAGES }}" &e; &e_header; %nt(1, s=40 40, h=1, w=6.5, hd=1, last=1); put &bc "{\fs28\b Listing 1: Smoking in Framingham Heart Study for the First 90 Observations}" &e; %nt(1, h=1, w=1, hd=1); **** hd=0 will turn off the header for page 2 and after; put &bc "{\b Smoking}" &e; %nt(1, h=1, w=1, hd=0); end; put &bc smoking &e; if eof then do; %nt(100); end; run; The %nt macro code was published in 1998 in SAS Observations 13, and an RTF output from the above program is also attached.     Thanks,  Jianmin Long   ... View more

Hi @JeffMeyers and @Norman21 ,    It's a great effort of Jeffrey to try an automated solution for this very difficult task, and the outcome so far is very helpful and promising.  I agree with Norman21 on 1) and 2).  3. has a bad link, and it probably refers to a Prashant Hebbar's paper, and here is one: https://www.sas.com/content/dam/SAS/support/en/sas-global-forum-proceedings/2019/3149-2019.pdf .    Hebba's work was amazing but not general enough and it's not about to automate this process.     Shane Rosanbalm' work, of Rho Inc.,  https://www.lexjansen.com/pharmasug/2019/DV/PharmaSUG-2019-DV-021.pdf,  is very closed to automate the process, he wrote 3 macros to handle the boxes, links and text positions and they are quite general.   Ryan Yu, of Regeneron, published a paper to claim he automated the process, using Shane's macros, https://www.lexjansen.com/pharmasug/2021/DV/PharmaSUG-2021-DV-082.pdf, but we haven't see the code yet.    Besides 1. and 2 from Norman21, Figure 3 in this link: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2222221/pdf/1745-6215-8-36.pdf is a little bit challenge for Jeffrey to try.    I have explored a different method to draw a CONSORT diagram.  See the attached.  It uses Microsoft Word/RTF's Shapes, boxes and arrows here and only SAS data _null_ was used in the generation of the file.  The outcome is an RTF file, but it's totally not what in Art Carpenter's head when he talked about using RTF file to automation of CONSORT diagram: https://www.lexjansen.com/pharmasug/2012/TF/PharmaSUG-2012-TF16.pdf   ... View more

Hi @varma1987, @Cynthia_sas  and @ballardw,    I really appreciate your question and the effort to solve the problem.  The solution requires a different implementation of Microsoft Word/RTF in PROC REPORT and the issue is related with the concept of 'breaking a cell across pages'.  The latest PROC REPORT document mentioned an option of this idea, and the Tech Support might have a solution for it.    Here is an example how Microsoft Word/RTF solves this problem:   I opened a Word document, insert a 3X3 table; I made the first row as Header row and allowed cell break in the second row (all in table option), nothing on the third row; and save it as an RTF file.    I made 3 headers (A, B and C) in the first row; copied the text of your question, and pasted it in the cell of second row and column B 3 times.  Now this cell grows big and across 2 pages.  See the attached for yourselves.    Also note Microsoft Word/RTF handles pagination very nicely, and you don't have to worry about where to break a page.  You can try your data in that cell and see how it is handled.     Many Thanks,  Jianmin Long ... View more