Hi:
At this time, I believe that the SAS Add-in for Microsoft Office (Excel) does NOT support a stored process that returns output from the ExcelXP destination. When I tested this a while back, a stored process that used TAGSETS.EXCELXP could only be executed from the Information Delivery Portal, the Stored Process Web Application, a custom application -- or MAYBE SAS Enterprise Guide. Generally, speaking, if you were going to use those client applications (or write your own app), you could code the stored process as one of the following:
[pre]
ods tagsets.excelxp file=_webout style=sasweb
options(sheet_name="mydata" frozen_header="2" autofilter="all");
...code ...
ods tagsets.excelxp close;
[/pre]
an alternative method would be:
[pre]
%let _odsdest = tagsets.excelxp;
%let _odsstyle = sasweb;
%let _odsoptions=%str(options(sheet_name="mydata" frozen_header="2" autofilter="all"));
%stpbegin;
...code ...
%stpend;
[/pre]
However, 1) you might need to use different invocations for different client applications and 2) you might need to send your own content-type header for web results, to tell the receiving machine to launch Excel for the output stream instead of the browser.
But, as I said, I do NOT believe that the Add-in for Excel will accept/receive tagsets.ExcelXP XML results at this time. For the final word on this subject, you can check with Tech Support. I don't know enough about Excel to know how you would implement frozen headers or autofilters from the Excel end instead of the SAS end.
cynthia