It seems that when I run an ODS HTML command, Enterprise Guide 4 will not return the results as HTML even though I have click that option in the Tools window.
Could it have something to do with the autoexec.sas?
To debug what is happening, you could open a code node in EG, paste this code into the code node and submit the following code (either on your local machine or on the server -- whichever one you were using when you discovered the problem):
ods _all_ close;
ods html file='testit.html' style=sasweb;
proc print data=sashelp.class;
title 'My Report';
ods html close;
The first statement closes any open ODS destinations and the next ODS HTML "sandwich" explicitly creates an HTML file. This program should create an HTML file inside your EG project.
If it does not work, then the log for this code may be instructive as to why you're getting errors. If for example, you get an error message about ODS HTML or the SASWEB style not being found, this might indicate some kind of error in the ODS PATH statement that points to the various template stores.
NOTE: There were 19 observations read from the data set SASHELP.CLASS.
NOTE: The PROCEDURE PRINT printed page 1.
NOTE: PROCEDURE PRINT used (Total process time):
real time 0.03 seconds
cpu time 0.00 seconds
This is not actually an ERROR, it is a WARNING and it tells you what is going to happen:
WARNING: Style AMODEFAULT not found; Default style will be used instead.
What it's saying is that the Default style will be used instead of AMODEFAULT style. It sounds like you are not running through JUST Enterprise Guide, but are using the SAS Add-in for Microsoft Office within the context of a Enterprise Intelligence Application configuration.
These kinds of questions are best answered by Tech Support because it sounds like you have 2 problems. A style warning should NOT prevent the results of a simple proc print task from showing in EG or in the SAS Add-in. So that's one problem. You need to get that resolved before the second question can be addressed -- how to point to a different style sheet location. And since this second question generally involves some work needed by the SAS Administrator to make files on the server available, your best bet for this answer is to read the Platform Administration guide or contact Tech Support for help.