Desktop productivity for business analysts and programmers

Styles and Internal vs External RTF files

Reply
N/A
Posts: 0

Styles and Internal vs External RTF files

I have a question about the output from submitting the following code in EG. My EG environment has RTF output requested in Tools / Options / Results and also sets the RTF default style to 'minimal'.

ods rtf style=brick;
proc print data=sashelp.class;
run;
ods rtf style=journal;
proc print data=sashelp.class;
run;

I thought this would create one RTF output stored in the .egp file with the 'brick' style applied first and then the 'journal' style applied. Instead, I see two output RTF tabs. One tab shows the RTF output that is stored in the .egp file. It uses the RTF default style for both steps. The other tab shows RTF output stored in C: \SAS\Config01\Lev1\SASApp\sasrtf.rtf. It shows the styles requested in the ods rtf statement. I know that I can use the file= option on the RTF statement to store the output in a more appropriate external location, but I'd prefer to keep the RTF output in the .egp file.

Is there anyway to have control over the styles used in different parts of the EG internal RTF output? In non-EG environments, I used the ods rtf statement to control the styles for different types of reports. A style that adds value for one type of report might not be good for every report. Is something like this possible in EG with internally stored RTF outputs?

Also, it would be much better if there were only one RTF output tab (without needing to change the default setting for the Results RTF destination). Is there anyway to see only one RTF tab when producing an external RTF file?

Thanks for any help,
Paulette
N/A
Posts: 0

Re: Styles and Internal vs External RTF files

The answer appears to be:

ODS RTF(ID=EGRTF) style=brick;
proc print data=sashelp.class;
run;
ods rtf (ID=EGRTF) style=journal;
proc print data=sashelp.class;
run;

You get one RTF output tab with the correct formatting.
Ask a Question
Discussion stats
  • 1 reply
  • 122 views
  • 0 likes
  • 1 in conversation