Hi:   I guess it comes down, for me, to this question: -- do you need some feature in TAGSETS.RTF that is NOT available in the original RTF   Answering that question is going to require some testing. On the other hand, if 90% of what you want is OK with ODS RTF, and you only need TAGSETS.RTF for the remaining 10%, then is it really worth switching everything to TAGSETS.RTF just to only deal with 1 destination. The beautiful thing about having 2 ODS destinations that created RTF output is the ability to create your output the way you want. For example, if you KNOW that you are going to have multi-page tables and you absolutely want the "Continued" at the bottom of every page,  where the table spills over to the next page, then that's an argument for TAGSETS.RTF. If your tables are "page-sized" or will fit on one page, then Continued is out of the picture, why not use regular ODS RTF?   Do you want the output to have "fixed page breaks" and wrapping, as set by SAS (ODS TAGSETS.RTF has vertical measurement so SAS page breaks are respected)? Or, do you want to allow the page breaks to depend on the Word margins (ODS RTF does not have vertical measurement).   If you want to have a table and a graph from the SG procedures side-by-side on one page, that is actually an argument for using ODS LAYOUT with ODS PDF (not ODS RTF).     Sorry, I don't have a one size fits all recommendation. I've been doing this too long to recommend hitching your output wagon to one destination and only one destination.   Cynthia   ... View more

Cynthia, This works fine, Thank you for your response. I hope others find the information usefull. Karen ... View more

Hi:    Actually, the ODS RTF CONTENTS= option inserts RTF control strings that correspond to the Word field codes for creating a TOC -- any word processor that knows how to render RTF control strings, should be able to create a table of contents, as long as the word processor supports the contents option.   The RTF specification was written by MIcrosoft, so the behavior you observe is puzzling.   ODS TAGSETS.EXCELXP is the ODS destination that creates Microsoft Spreadsheet Markup Language 2003 XML So, if you use CONTENTS= with TAGSETS.EXCELXP, you get XML generated. But, if you use CONTENTS= with ODS RTF, you get RTF control strings that roughly correspond to MIcrosoft Word field codes.   This actually sounds like an issueto report to Tech Support. If there is a bug that needs to be fixed, Tech Support can report it to the RTF developers. cynthia ... View more

Thank you for sharing this! ... View more

Hi: Are you doing this as a stored process or using SAS/IntrNet??? If the issue is intermittent, then I think your best bet for a solution is to work with Tech Support to figure out what is intermittently causing the Dispatcher program or stored process to fail. cynthia ... View more

Hi Cynthia, I tried your suggestions, plus the ones in the paper and from the website link. It seems to be more of a MSword issue. Once that file is replaced, then I will test again. Thank you for your help and examples. Karen S ... View more

Hi, Here's the thing... I still can't quite visualize what you are attempting, but I think you will need ODS Layout. You still might want to work with Tech Support to see whether what you want is achievable. Cynthia ... View more