Okay, first of all thanks to everyone who replied all of your suggestions were helpful. I talked to a coworker and we do run SAS on a UNIX server which must be why the EXCEL engine is not working. I did get an error when using: libname myRef PCFILES path='path to excel file'; my coworker suggested adding: SERVER = &_clientmachine.; and that resolved the errors and I was able to export to a named range.   However, now my issue is that SAS includes the variables names as the first row in the exported range. Here's the form of the code I'm using: /*Define libname to output workbook*/ libname WrkBk PCFILES path="path to excel file" SERVER=&_clientmachine.; /*Clear existing data from desired named range*/ proc datasets lib=WrkBk nolist; delete namedRange; quit; /*Export data to Excel*/ data WrkBk.namedRange; set importDataSet; run; libname WrkBk clear; From what I've read there isn't an option to not include variable names using a data step and using putnames = no in a proc export statement doesn't seem to be able to do what I want. I know this macro: http://www.sascommunity.org/wiki/Excelling_to_Another_Level_with_SAS would do what I want, but I haven't had any success running it in Enterprise Guide.   It appears my options are as follows: The quick and dirty option: hide the first row of the named range and pretend like it doesn't exist. Use ODS to recreate the template. Use SAS to export to a text file and VBA to import that into the template. Any other suggestions or corrections would be much appreciated. ... View more