- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I am trying to generate an excel file with this code:
ods html file="/home/&x rpt.xls" headtext="<style>
td {mso-number-format:\@}</style>";
proc print data=&x uniform label;
run;
ods html close;
&x is the macro that resolves to a name of a table.
When i generate this file on a unix box and copy the excel to a windows box and try to open it, I get warning:
The file you are trying to open is in a different format than specified by the extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file now?
When I click 'Yes', it opens fine.
My guess is that it is because in the ods, i say html and then save it as xls.. How to get around it?
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
None of the ODS destinations generate a "native" excel file.
You can convert it on the windows side, not sure about Unix.
43496 - Convert files created using an ODS destination to native Excel files
It looks to be just a proc print, so why doesn't a proc export work?
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
This is because of the new Excel security feature beginning with Excel 2007 that matches the content and the extension. You can use the ExcelXP tagset and use the.XML extension, otherwise it would take a registry change to prevent the warning. See the below for more information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Thank you. But i was hoping for an excel file and not an xml file as output.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
None of the ODS destinations generate a "native" excel file.
You can convert it on the windows side, not sure about Unix.
43496 - Convert files created using an ODS destination to native Excel files
It looks to be just a proc print, so why doesn't a proc export work?