I've mentioned that to them already, along with the data step report writing interface.  I will probably end up going with one of those solutions.  But, it's been 15+ years since I did anything with TABULATE and didn't want to give up without checking for anyone having a creative solution. ... View more

I did hear from SAS tech support that this is caused by "some recent Windows updates that have corrupted the Microsoft Ace Engines."  For me the workaround was to uninstall the Microsoft Access Connectivity Engine and reinstall the Office 2013 version (AccessDatabaseEngine_X64.exe).  Tech support said that Microsoft is working on a fix. ... View more

Thanks Tom - you are correct.  I've always used RANGE with DBMX=Excel and you get away with just referencing a worksheet name (with no range specified) and IMPORT will read the entire sheet.  With DBMS=XLSX the RANGE= statement needs to specify a range, but the SHEET= statement works fine with XLSX to read the whole sheet.   While this does work, I've tracked down about 150 places in my code I've used DBMS=Excel that might have issues.  Fortunately, the IMPORT always works when just called once, so often not a real issue. ... View more

XLSX on PROC IMPORT is not really an option for me in the real world as, at least last I checked, it does not support reading from a specific worksheet.  It will always read from the first one and many of the spreadsheet I'm pulling data from have multiple worksheets and I need to reference particular ones. ... View more

I'm amending my earlier post - this does fail in DM as well.  I created a simple two-cell spreadsheet with a "header" row of "Quote" and a data "row" of "Hello World!" in c:\temp\HelloWorld.xlsx and am running PC SAS on the same machine.  In either EG or DM the following code runs just fine once or twice and then fails.  In EG, I get the "Lost connection to server" message and in DM, the session just goes away.  I get the exact same behavior on two different machines.   PROC IMPORT OUT= WORK.ComorbidityLabels DATAFILE= "c:\temp\HelloWorld.xlsx" DBMS=EXCEL REPLACE; RANGE="Sheet1$"; GETNAMES=YES; MIXED=NO; SCANTEXT=YES; USEDATE=YES; SCANTIME=YES; RUN;   And a new wrinkle, it's not just PROC IMPORT.  I get similar results using the Excel LIBNAME engine.  This code runs fine two or three times and then fails:   libname test excel "c:\temp\HelloWorld.xlsx"; data test;   set test.'Sheet1$'n; run; libname test clear;   In EG, sometimes I get the server connection lost message and sometimes a different message, "Error: Integration technologies failed to provide server interface. The remote procedure call failed. (Exception from HRESULT: 0x800706BE)"   I'd be interested if anyone can run either of the above a number of times in a row with success on a similar setup: PC SAS 9.4M7 on the local machine, Windows 10 Pro, Office 365.  Again, I have the same issues on two different machines and the real code that exposed the issue has been running unchanged for months and this just popped up this week. ... View more

As I mentioned in my post, everything, SAS and data, is local (on the same machine).  I'm the "SAS administrator" as it's a PC SAS  license on one workstation.  The job literally takes a fraction of a second to run, returning about 20 rows from the spreadsheet - hardly time for the connection to get hung up.  The main thing though is that this job has run thousands of times and just started doing this yesterday - no changes to SAS or EG installs.  I'm think it's a Microsoft update issue, but am having trouble seeing how this would affect EG differently than DM. ... View more

I'm having a very similar issue, but using PROC IMPORT with EXCEL rather than EXPORT.  The following code is the result of a macro call, but I have the same issue whether the code is run from the macro call or just run itself:   PROC IMPORT OUT= WORK.ComorbidityLabels DATAFILE= "\\coconuts3\data\AlaskaTrauma\ProjectFiles\Control\AnnualReportLabels.xlsx" DBMS=EXCEL REPLACE; RANGE="ComorbidityLabels$"; GETNAMES=YES; MIXED=NO; SCANTEXT=YES; USEDATE=YES; SCANTIME=YES; RUN;   If I run this in EG, where the macro that creates the IMPORT code is generated, I randomly get a "Error: The connection to the server has been lost."  This code has run just fine for many months and just yesterday started acting this way.  The code runs fine in DM.  SAS and all the data are on the same machine.  Using 9.4M7 and EG 8.3.0.103. ... View more

I totally agree with Lori. Speakers this past year were asked to have the first slide of their presentation be their bio - eliminating the need for often-clumsy introductions by session volunteers. That was a great idea. Maybe we could have the last slide be a reminder to leave feedback - assuming, as Lori points out, that it's super easy to do. ... View more

...and becoming inspired at that "show", you'll want to catch a great follow-up act: http://www.sas.com/en_us/events/sas-global-forum/sas-global-forum-2016/training/sas-tutorials.html#m=reporting-your-way-with-the-report-writing-interface ... View more