Hi:
TAGSETS.TABLEEDITOR uses HTML with embedded JavaScript. If you can load your browser with HTML files that have embedded JavaScript to do the creation of an HTML file, this solution may work. However, I believe that the HTML file must load into the browser first before the JavaScript "Export/Save" button becomes active.
Information on TAGSETS.TABLEEDITOR is here:
http://support.sas.com/rnd/base/ods/odsmarkup/tableeditor/index.html
and
http://support.sas.com/rnd/base/ods/odsmarkup/tableeditor/index.html#exporte (see the suboptions EXCEL_SAVE_FILE and UPDATE_TARGET starting at this location in the description of TAGSETS.TABLEEDITOR)
As for the other methods -- OLE-DB, ODBC, DDE, creating Microsoft XLT files -- those are all Microsoft topics. To the extent that you can use OLE-DB, ODBC and/or DDE with SAS -- you are basically sending Microsoft commands to Excel using a "conversation" between two applications. If you are using SAS in a client/server scenario -- such as EG on Windows and SAS on Unix, then you may not be able to use DDE, etc, because I believe both apps have to be talking to each other on the same system for the "conversation" to take place.
There are some user group papers on DDE, ODBC, OLE-DB, etc -- probably more DDE examples than anything else out there.
(If you do a Google search on:
Koen Vyverman SAS DDE
or
Leroy Bessler SAS DDE
you should find some good papers.)
It looks to me like TAGSETS.MSOFFICE2K_X will allow you to load an Excel macro when the file is opened or closed -- this may be another alternative -- if your clients allow the use of Excel macros -- it might be a simple Excel macro as described here:
http://support.sas.com/rnd/base/ods/odsmarkup/msoffice2k/index.html#Macro (of course that means the Excel macro would also have to be written and resident on the user's system).