Greetings, My apologies if these have been asked elsewhere. I did some searching and didn't see anything similar. I am migrating a bunch of ods rtf reports I inherited from 9.3 -> 9.4, and I'm getting different output on the newer system. Researching the issues, I can't seem to find SAS configuration changes which would resolve the issue, but I may just be missing something. 1) I have a report that does soemthing like the following: ods path <location which contains only a custom style specific to this report>; ods rtf file=... style=<previously defined custom style for the report> ... ; proc report; ... compute before pg; ... etc. Text specified in the compute block is printed using the linecontent style element. However, the custom style specified does not contain a linecontent section, nor does it inherit from any other style. In 9.3, the resulting text gets printed using Times New Roman, while in 9.4 it gets printed as Courier. However I am uncertain as to why there is a difference. Is there any way to configure ods' behavior in the case where no style has been defined for the element? The ODS path configuration seems to rule out the implicit parent: base.template.styles I can simply add a linecontent section to the custom style, but it would become onerous to modify the code for all the reports, so I was curious if the default can be set somehow. 2) In a different report there's something like this: proc report; ... define name / "Name" display center style={just=l width=7}; ... In 9.3 the report used the width value specified without a dimension in a certain way. Experimentation suggests that it was using it as a % . In 9.4, it appears to be using the width value in a completely different way. If I alter the code to include a % for all rows define name / "Name" display center style={just=l width=7%}; etc. I get output which resembles the 9.3 output. Is there anyway to set the default dimension which ODS uses for width values without one specified? Or a SAS option to force 9.3 like behavior? I can simply modify the code manually to include the %s but, again, it would be onerous to do so across all the reports. Regardless, pleas let me thank you for your time as well as any suggestions you might have.
... View more