Hi: The issue is not FILE= vs BODY= -- they are aliases for each other and are not the problem. It seems to me that you are experiencing this problem: http://support.sas.com/kb/15/046.html where your default location for HTML output has been modified to your C:\users directory and so that information is now "prepended" to your FILE= path. This results in the error message that you see and in the full PATH appearing twice in your LOG. You have 2 choices for a solution: 1) (probably the simplest) use ONLY the file name in the FILE= option: ods html file='myfile.html'; or ods html file='myfile.xls'; and let the Registry setting provide the path location OR 2) use the PATH= option to explicitly override only the directory path that is coming from the SAS registry (note that the directory you specify must exist): ods html path='c:\temp' (url=none) file='test_to_excel.xls' style=sasweb; proc print data=sashelp.class; run; ods _all_ close; So, either way, one of those options should work. If you continue to have issues, you might want to work with Tech Support. FYI -- PROC EXPORT and ODS create very different types of files for Excel to open. PROC EXPORT creates a true, binary Excel proprietary format file. On the other hand, ODS HTML (or any of the HTML destinations) creates an ASCII text file in HTML format which Excel knows how to open. You are merely "fooling" the Windows registry into launching Excel when you give the HTML file a .XLS extension. Also, ODS HTML creates HTML 4.0 compliant tags. Microsoft Excel is not as "happy" to open these type of HTML tags as it is with other types of HTML, either of these 2 destinations creates HTML output that Microsoft is generally "happier" to open: ODS HTML3 (produces HTML 3.2 tags) or ODS MSOFFICE2K (produces Microsoft "flavor" of HTML) Also, if you do NOT care about colors and fonts that come from the style template, you can also use ODS CSV to create a comma separated file for Excel. cynthia
... View more