07-18-2007 09:26 PM
07-18-2007 11:54 PM
07-16-2014 11:12 AM
In my case we will update the excel and we should import it back to sas. By chance is there any work around for this to import?
07-16-2014 02:40 PM
I have the same issue. The only work around I found is to have the user make their updates to the exported XML file, use the Save As command in Excel to save it as a XLS or XLSX file, and send it back to me.
07-16-2014 03:03 PM
Hi, you have responded to and reactivated a 7 year old posting. It would be much better for you to start a new post with your question and refer to this post. However, the answer is still the same. You don't need a "workaround", you need to adjust to the reality of using TAGSETS.EXCELXP. That ODS destination (TAGSETS.EXCELXP) does NOT, NOT, NOT create a true binary Excel file that can be imported. So your choices are:
1) create the XML file using TAGSETS.EXCELXP and manually or with a VBScript program save the file as proprietary .XLS or .XLSX
2) create the XML file using TAGSETS.EXCELXP and manually export the file to CSV format and read the CSV file back into SAS
3) create the XML file using TAGSETS.EXCELXP and use SAS XML Libname Engine with an XML Map to import the XML file back into SAS, as described in this paper http://www2.sas.com/proceedings/sugi31/115-31.pdf