Hi: I would recommend that you work with Tech Support. Someone will have to actually look at your data or test data that replicates the issue. They will need to see how you create the pagetext and pagetext2 variables and what their values are as the calculated page changes and the values of all your macro variables in order to try to understand what's happening. I note that you are using @ pointer control in your LINE statement -- in my experience, this works better with LISTING than with any other destination. I also note that you are using options like WIDTH, HEADLINE, HEADSKIP, SPACING, etc, which will also be ignored by a non-LISTING destination like RTF. I do not see the use of the PAGE option on the DEFINE statement, but I do see the use of the PAGE option on the BREAK statement, so that explains why the subject line of your original post was confusing and why I referenced the irrelevant note. It was my understanding that TAGSETS.RTF was created to allow for the vertical measurement of pages in your SAS output, so that the page break that SAS inserted into the RTF file would be used by Word. The technique that you show (making your own page break variable) was the type of technique used before TAGSETS.RTF (or measured RTF) was introduced. The TAGSETS.RTF destination has several features that make it seem more compatible with what you want to do: 1) automatically inserts a continued line by default by a table breaks across pages 2) puts a title and footnote in the appropriate places, using the SAS TITLE and FOOTNOTE statements (instead of a COMPUTE block) and the TITLE and FOOTNOTES are not placed in the header of the document when Word opens the file I think that investigating TAGSETS.RTF would be worth your effort, as it might simplify your code. cynthia
... View more
