XML Errors from ExcelXP

[NCNyrk]

I had successfully been using the previous 2006 version of the ExcelXP tagset, but my XML files were larger than I had hoped. I remember reading that the new version from 2007 would have some better compression. I was able to get the new tagset loaded, but am now getting XML errors in the XLS files I create (same program...no other changes except new tagset lib)...any ideas what is going on?


XML ERROR in Style
REASON: Too many tags
FILE: C:\Documents and Settings\kjk4\Local Settings\Temporary Internet...
GROUP: Styles
TAG: Style
ATTRIB: ID
VALUE: data_c

XML ERROR in Style
REASON: Bad Value
FILE: C:\Documents and Settings\kjk4\Local Settings\Temporary Internet..
GROUP: Styles
TAG: Style
ATTRIB: Parent
VALUE: data

[Eric_SAS]

Hello,

There were numerous changes to the style handling to allow for justification. It looks like you might have run into a problem with it. I have seen one other problem similar to this but it doesn't
look quite the same. I may have fixed it already or maybe not.

Can you provide a simple test that shows the problem? I am currently at the SAS Global Forum.
If you are there, come by the ODS booth.

[NCNyrk]

Not certain what you want to see...here is a code sample that worked previously but no longer does:

ODS TAGSETS.EXCELXP FILE=OUTXLS STYLE=STYLES.XLStatistical
TRANTAB=ASCII;

%LET L = 1;
%DO %UNTIL (%QSCAN(&EVTLST,&L)=);
%LET EVT = %UNQUOTE(%QSCAN(&EVTLST,&L));

ODS TAGSETS.EXCELXP
OPTIONS (SHEET_NAME="&EVT &RPTST RESIDENTS"
FROZEN_HEADERS='1' ROW_REPEAT='1'
CENTER_HORIZONTAL='Yes'
ABSOLUTE_COLUMN_WIDTH='6,16,7,16,20,9,5');
TITLE1 "&&ENAME&EVT &&PROC&BATCH";
PROC PRINT DATA=ALLEVT NOOBS LABEL SPLIT='/';
WHERE FSTATRES = "US&RPTST" AND EVENT = "&EVT";
VAR YEAR / style=data_c;
VAR FSTATOCC;
VAR FILENO / style=data_c{tagattr="format:000000"};
VAR FSTATRES FCNTYRES;
VAR DATE / style=data_c;
RUN;

%LET L = %EVAL(&L + 1);
%END;
ODS TAGSETS.EXCELXP CLOSE;

[Eric_SAS]

That may be enough. I'll try to reproduce it.

That is what I need. Something specific enough to
reproduce the problem.

Eric

[NCNyrk]

Should I refer this to Tech Support directly?

Thanks,
Kryn

[Chevell_sas]

Hello Kryn,

Open a tracking entry with Technical Support for this problem. Be sure to send the file which generates this dialog error.

Chevell