MSOffice2k creates much bigger file sizes in SAS 9.2 than in SAS 9.1.3

[Catrin]

Hallo,

we use MSOffice2k tagset to create files using in Excel 2000.
After migration to SAS 9.2 file sizes are much bigger. There are examples that the files get so big now, that Excel cannot read it. Looking into the generated HTML files we can find the reason for the file size differences. Is there an option to tell msoffice2k tagset to
create the files like in Version SAS 9.1.3 ?

Please find here an SAS-Code Example:

ods listing close;

ods markup file="/u/m500843/sassrc/msoffice2k_9-2.html" tagset=msoffice2k;

proc freq data=sashelp.prdsale;
tables COUNTRY*REGION*DIVISION*QUARTER*PRODUCT*PRODTYPE;

run;

ods markup close;

ods listing;

In SAS 9.1.3 the size is about 233 kb, in SAS 9.2. 633 kb

Kind regards Catrin

[David_SAS]

Catrin,

PROC FREQ makes use of stacked cells. The way ODS generates stacked cells changed from SAS 9.1 to SAS 9.2. The behavior you're observing is by design.

Contact Tech Support by clicking on 'Contact Us' at the bottom of this page if you have further questions.

-- David Kelley, SAS

[Catrin]

Hallo David,

thank you for answering. I assumed that it works as designed. This means to me if Excel crashes because of the big file sizes we have no other chance than to change to another tagset. Is this the case?
With regards
Catrin

[sbb]

This is one of those nuances (gently keystroked for the forum readers) with SAS software and the trade-off with embracing new approaches/ideas/technologies as compared to upward-compatibility for your SAS application code.

The SAS Base component ODS is ever-changing with improvements (some would say), and some are communicated while others are not so obvious (for example, VBAR vertical bar spacing default change with SAS 9.2).

So, this post/thread is one indication that when changing SAS versions (even at the Service Pack level), sufficient testing with the SAS facilities, procedures, and technical aspects one uses is up to the end-user or their support staff. And, do make use of the extensive SAS.COM support website resources when planning / executing a version and/or maintenance-level change.

Scott Barry
SBBWorks, Inc.