I see. I was trying to re-input the date unnecssarily. This works beautifully. Thank you! ... View more

This was perfect and worked like a charm!   Thank you so much. ... View more

PG,   Thank you for the response. The output did not necessarily accomplish my   Thank you for your advice though!   josh@123gmail.com 0 josh@jeoiafwgmail.com.bu 0 josh@a09irafyahoo.com 0 josh@a09irafaol.com 0 ... View more

Reeza,   That's a good question.   Reason being is because occasionally the record-level data will present emails like this:   josh@123gmail.com josh@jeoiafwgmail.com.bu josh@a09irafgmail.com   I still want to be able to capture those. ... View more

Thanks SASKiwi. This was a unique problem that we ran into, and in the future we're going to restructure our coding algorithms to use character strings instead. ... View more

Thanks Chris! This was exceptionally informative and helpful. ... View more

That's very prudent insight.   I agree-- excel is not a reporting suite, but when it comes to analysis, oftentimes you find that ubiquity is key. (translation: this is the format my bosses want it in).   1) Spotfire isn't free. 2) That's what I'm trying to do, but the XLSX is being overwritten 3) This might be the only option. I'll export it to a seperate xlsx, and then use a vbscript to import it into the main folder ... View more

*forehead slap. Thanks Reeza. I'll take a look at the Wiki! ... View more

Does this code overwrite the existing workbook? I want to keep the other sheets, and just replace one of them.   Also, the first line in the command results in an error.   16 17 %utlfkil(d:/xls/existing_sheet.xlsx); _ 180 ERROR 180-322: Statement is not valid or it is used out of proper order. ... View more

I attempted to run it in a specified range, and the query ran successfully, however it ended up overwriting the entire workbook.   ... View more

Reeza,   The put function doesn't seem to reveal the SAS Version number.    I attempted to run using the DMBS = EXCEL, and I received a class not registered error.   %put &sysver; PROC EXPORT DATA= dash.sum_taxonomy outfile= "\\server\Dashboard.xlsx" dbms=EXCEL; sheet="RawData"; NOTE: Writing TAGSETS.SASREPORT13(EGSR) Body file: EGSR 13 14 GOPTIONS ACCESSIBLE; 15 %put &sysver; 9.3 16 PROC EXPORT DATA= dash.sum_taxonomy 17 outfile= "\\server\Dashboard.xlsx" 18 dbms=EXCEL; 19 sheet="RawData"; 20 21 22 23 24 GOPTIONS NOACCESSIBLE; 25 %LET _CLIENTTASKLABEL=; 26 %LET _CLIENTPROJECTPATH=; 27 %LET _CLIENTPROJECTNAME=; 28 %LET _SASPROGRAMFILE=; 29 30 ;*';*";*/;quit; 1 The SAS System 15:49 Wednesday, August 17, 2016 ERROR: Connect: Class not registered ERROR: Error in the LIBNAME statement. Connection Failed. See log for details. NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE EXPORT used (Total process time): real time 0.05 seconds cpu time 0.01 seconds   I attempted to run on EXCELCS and received the following error:   %put &sysver; PROC EXPORT DATA= dash.sum_taxonomy outfile= "\\server\Dashboard.xlsx" dbms=EXCELCS; sheet="RawData"; NOTE: Writing TAGSETS.SASREPORT13(EGSR) Body file: EGSR 13 14 GOPTIONS ACCESSIBLE; 15 %put &sysver; 9.3 16 PROC EXPORT DATA= dash.sum_taxonomy 17 outfile= "\\Server\Dashboard.xlsx" 18 dbms=EXCELCS; 19 sheet="RawData"; 20 21 22 GOPTIONS NOACCESSIBLE; 23 %LET _CLIENTTASKLABEL=; 24 %LET _CLIENTPROJECTPATH=; 25 %LET _CLIENTPROJECTNAME=; 26 %LET _SASPROGRAMFILE=; 27 28 ;*';*";*/;quit; 1 The SAS System 15:51 Wednesday, August 17, 2016 ERROR: CLI error trying to establish connection: [Microsoft][ODBC Excel Driver]General error Unable to open registry key Temporary (volatile) Ace DSN for process 0x6730 Thread 0x5914 DBC 0xcb89b4 Excel'. ERROR: Error in the LIBNAME statement. Connection Failed. See log for details. NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE EXPORT used (Total process time): real time 0.27 seconds cpu time 0.00 seconds 28 ! run; 29 ODS _ALL_ CLOSE; 30 31 32 QUIT; RUN; 33 ... View more