But you cannot have both the 32-bit and 64-bit versions of these data providers on the same machine; if you have 32-bit Microsoft Office, then you're stuck with the 32-bit providers for now.
The second remedy is to use the PC Files Server, right there on the same Windows machine where SAS is running.
These methods use features of SAS/ACCESS to PC Files: LIBNAME EXCEL – reads/writes Excel files at the sheet level when the bitness of SAS (32- or 64-bit) matches the bitness of Microsoft Office installed (or more specifically, the ACE drivers that accompany Office).
An Excel file is viewed as a SAS library, while sheets/ranges are the member tables. LIBNAME PCFILES – does the same as LIBNAME EXCEL, but uses PC Files Server.
This allows a 64-bit SAS process to delegate the data exchange to a 32-bit PC Files Server process.
SAS offers many ways to read from and write to Microsoft Excel spreadsheets. This post is an inventory of the methods that I know about for Excel files from within SAS.Before I get to the Big List, let me set the stage by describing a few terms and concepts.In order to create Excel files directly from SAS, you need SAS/ACCESS to PC Files.There are various options to control the output behavior. Provides a fair amount of control over the content appearance, but recent versions of Excel do not recognize as a "native" format, so user is presented with a message to that effect when opening in Excel.Good for UNIX and for Windows configurations where bitness of SAS and Microsoft Office don't match. The following methods require SAS/ACCESS to PC Files, so they are popular, even if they don't produce "native" Excel files: PROC EXPORT DBMS=CSV – produces comma separated value files, most often used in Excel. CSV (or just DATA step and FILE output) – produces comma separated value files, most often used in Excel. FILENAME DDE – uses Windows messages to control what goes into an Excel file, down to the cell level.