Stop Statement from Producing ODS RTF Output

[tburus]

I have a large data report where I am opening the ODS RTF output file and then calling several files using %include to fill in the content. These documents contain various data manipulations, followed by the output I desire to have. All of them run fine with the exception of one. In that file I am using a number of statements similar to the following:

ods exclude all; 
ods output OddsRatio(persist=proc)=odds_basb_act(where=(Statistic="Column 2 Relative Risk"));
proc surveyfreq data=GLSDesign_basb3;
   	strata strata;
	weight nationalweight;
	tables sport_name_girls_softball*(act_:)/ or noprint;
run;
proc surveyfreq data=GLSDesign_basb3;
	strata strata;
	weight nationalweight;
	tables sport_name_boys_baseball*(act_:)/ or noprint;
run;
ods output close;
ods exclude none;

I expected this to be ignored by the output, but instead it appears to be creating a blank line (or several) in the ODS RTF output every time it runs. How can I correct this?

[ChrisNZ]

Have you tried this
To temporarily suspend a destination, use ODS SELECT NONE. Use ODS SELECT ALL when you want to resume sending output to the suspended destination.
as stated in the documentation?

[tburus]

After your comment I did, but it made no difference. Thanks for the suggestion, though.

[ChrisNZ]

Sorry, no more idea. Maybe @Cynthia_sas has one?

[Cynthia_sas]

Hi:
Well, have you tried doing the SURVEYFREQ steps completely outside of the ODS RTF "sandwich". For creating some procedure output at least one destination has to be open in order for the procedure to run. I'm not sure of how SURVEYFREQ works but that might be one of them. I assume you want to get the output from the ODS OUTPUT statement to use with ODS RTF in some way, so my tendency is to let everything go to ODS HTML, which is usually the default and then do all my intermediate work so the output goes there for checking and then I put only the step I want inside the ODS RTF destination statements. But like I said, you may have tried that already and found it undesirable for some reason.
Cynthia

[tburus]

Thanks for the information. Yes, I did remove it from the ODS RTF sandwich and the issue went away. This is doable, but something I was trying to avoid.because it disrupts the normal flow of the overall document—a report where each section has been created as a stand-alone file including its own data work followed by RTF output, all glued into a master using %INCLUDE. The PROC SURVEYFREQ serves to generate relative risk CIs that are included in a data table used in a PROC REPORT statement. To get this issue to go away, I separated the data and desired output portions into two files for that section and ran the data portion before the initial opening of the ODS RTF output in the master file.