Did you get anywhere with Tech Support? I can see the problem in the XML: As the cells are written into the XML they are assigned sequential index numbers, but when you use the mergeacross option Excel expects the cells that are being merge to be ommitted from the sequence. i.e. in a 3 column table the cells are defined as <cell ss:Index="1"></cell> <cell ss:Index="2"></cell> <cell ss:Index="3"></cell> if merge across is set on col 1 then col 2 should be omitted to give: <cell ss:Index="1" ss:MergeAcross="1"></cell> <cell ss:Index="3"></cell> However in the XML created by SAS the cell with index 2 is still there. What we need is some way of getting the tagset to not output columns that are 'underneath' the merged across cell. I've tried to fool sas with columns defined with noprint in proc report, but it kindly shuffles everything along. Jon
... View more