Thanks very much Cynthia. That help to me .  Thanks again  ... View more

Thanks so much. ... View more

At the beginning of the DATA step, transfer the value of the macro variable to a DATA step variable: Custname = symget('custname') ; You will have no trouble working with a DATA step variable that contains an ampersand. ... View more

Hi:   It seems to me that you want something like this:   which was done with 2 PROC REPORT steps. The first PROC REPORT did the tables using PAGE for Canada and Pacific and the second PROC REPORT just did the Grand Total line.   Using this code: I think that this might be easier code to maintain because when I looked at your code, it seemed to me that you can probably get 25 obs on every page except for the last page because you've increased the font size for those last lines. So if you had a small number of rows on the last page, then the calculated pagex might be correct and there would be enough room on the page for everything. But if the last page does have close to 25 rows, then I believe the pagex you calculate can be "off" from what PROC REPORT actually produces when it's putting report rows into the PDF file.     Hope this helps, Cynthia   ... View more

Hi, PROC REPORT, I think, uses the NoteContent Style element -- so your template is probably not setting the correct element. I generally recommend that you try defining the LINE style in the PROC REPORT statement first before moving into TEMPLATE. You could set a default in the PROC REPORT statement and then use a different style specification on a COMPUTE statement. cynthia   ** in the code below, a default is set and then different LINES will get different styles.; ** you cannot do this in PROC TEMPLATE; proc report data=sashelp.class style(lines)={color=purple font_size=14pt}; compute before _page_ / style={font_size=10pt}; line 'BEFORE PAGE'; endcomp; compute before / style={font_size=8pt color=red just=l}; line 'BEFORE DATA'; endcomp; compute after _page_ / style={color=blue}; line 'AFTER PAGE'; endcomp; run; ... View more

If you already have the license for ODBC, why can't you use that instead? ... View more

Thanks very much , it cleared my confussion.     Thanks   Inp ... View more

Hi,   ODS ESCAPECHAR was available in late version 8, but the syntax was different. Instead of what Bruno used in his code with a "function-like" style override using ODS ESCAPECHAR and in-line formatting, the original syntax was a bit different. For one thing, it wasn't like a function call and for another, you couldn't nest style overrides. But I have many examples of the original style ODS ESCAPECHAR in this 2007 Global Forum paper on ESCAPECHAR: http://www2.sas.com/proceedings/forum2007/099-2007.pdf, which has comparisons to the "new" syntax. So you can work backwards from the new to the original syntax. cynthia ... View more

Hi: I posted some thoughts over in that other thread. cynthia ... View more

Thanks very much Ksharp and data _null_. Both is working to me. Thanks very much. Doney ... View more

Hi: I will try to do my best to explain what we do....   Firstly, we are using tagset 186 as our production tagset and we are using 9.1 as our production release, although this has been testes on 9.3 successfully. In the tagset, we have made the following changes starting at line 3349 of the code (the lines with the comments are the changes from the original code): define event align_tag; start: break /if $align_tag; put '<Alignment'; do /if cmp($cell_class, 'systemtitle');                   /* DD */ put ' ss:Wraptext="0"';                               /* DD */ else /if cmp($cell_class, 'data');                        /* DD */ put ' ss:WrapText="0"';                               /* DD */ else;                                                     /* DD */ put ' ss:WrapText="1"';                               /* DD */ done;                                                     /* DD */ set $align_tag "True"; finish: break /if ^$align_tag; putl '/>'; unset $align_tag; end; Then, in the code that generates the report titles, you code something like:   title1 'Left Portion Of Title'          '</Data></Cell><Cell ss:StyleID="systemtitle" ss:Index="6"><Data ss:Type="String">'          'Cenetered Portion Of Title'                       '</Data></Cell><Cell ss:StyleID="systemtitle" ss:Index="14"><Data ss:Type="String">'          'Right Portion Of Title'; (Just cut and past this as the title - that's how it got here). The left portion would start in relative cell #1, the centered portion starts in cell #6 and the right portion starts in cell #14. The positions of the cells on in the resulting spreadsheet would depend in the absolute widths of the cells if specified in the ExcelXP options. Let me know if you have any problems with this.  It has worked for us for may years. ... View more