Hi PSI_frank, Can you describe the big picture of what you are trying to do?  Is it that you are trying to get a stored procedure to write a "native" Excel file?  Looks like the current design is have stored process write a file using tagsets.ExcelXP, and then the VB script opens the file in Excel, and saves it as a native format (.xls or .xlsx)? Didn't see an answer to whether your SAS server is running on Windows or *NIX or other? Might ask yourself whether it is really important to have a native Excel file rather than an xml file with an .xls extension which Excel is happy to open. That said, if you really do want a native Excel file, and cannot run the VB script on the server, you might be better off separating the process into two steps.  So stored process could run on server and return xml file(s) to the windows world.  Then you could run your vb script in Windows to convert the files. I suppose another option would be to play with the addin.  When a stored process is run from the add-in the results come back via xml (SASREPORT format), but end up in a native Excel spreadsheet.  And I suppose if you wanted to you could use VB to script Excel to run the stored process, as in: http://www.lexjansen.com/wuss/2011/datapresentation/Papers_Beese_T_76227.pdf HTH, --Q. ... View more