topic Re: PROC EXPORT DBMS=EXCEL in SAS Procedures

PROC EXPORT DBMS=EXCEL

hellind — Mon, 30 Oct 2017 06:04:58 GMT

My version of SAS is base SAS 9.2

Windows 7 64 bit

Office Excel 2013 32-bit

SAS/ACCESS to PC Files is installed

This code use to work correctly but now I am getting error

ERROR: Connect: Unexpected error from external database driver (1).
ERROR: Error in the LIBNAME statement.

proc export data=dt.volumeEntity3 outfile='D:\SAS\workplan\output_crosssell.xls' dbms=excel replace;
run;

Re: PROC EXPORT DBMS=EXCEL

andreas_lds — Mon, 30 Oct 2017 08:26:49 GMT

Please post full log, especially with the libname statement for "dt".

Re: PROC EXPORT DBMS=EXCEL

RW9 — Mon, 30 Oct 2017 09:35:45 GMT

Whilst this is not your issue (from what I can tell from the brief bit posted) as your issue relates to the libname you haven't supplied, in your code you state output file is .xls - xls is a file extension for < 2003 Excel, it is the old binary file format. dsbms=excel should create .xlsx files, or Open Office file format, so ensure the file extension matches the file type. Shouldn't matter in this case, but might switch the engine if your not careful, and anyone using the file will be thrown off by the mismatch.

Re: PROC EXPORT DBMS=EXCEL

hellind — Sat, 04 Nov 2017 07:38:24 GMT

Which libname shoud I supply?

libname dt 'd:\sas\dt';

It is working. It is a local folder.

And this code used to work before.Suddenly it stopped working.

Re: PROC EXPORT DBMS=EXCEL

RW9 — Mon, 06 Nov 2017 09:19:39 GMT

Actually, a quick search shows it seems to be a Microsoft issue:

https://blogs.msdn.microsoft.com/dataaccesstechnologies/2017/10/18/unexpected-error-from-external-database-driver-1-microsoft-jet-database-engine-after-applying-october-security-updates/

As I mentioned before with the filename, use the correct file extension and this should solve it, if not follow m$ advice:

proc export data=dt.volumeEntity3 outfile='D:\SAS\workplan\output_crosssell.xlsx' dbms=excel replace;
run;

Re: PROC EXPORT DBMS=EXCEL

hellind — Mon, 11 Dec 2017 05:55:01 GMT

The issue is resolved after the recently downloading the new Microsoft Update.