Problem Note 40597: The SAS® PC Files Server engine ignores the FILENAME statement even though the SAS® log indicates that files are created
The EXCELCS and ACCESSCS engines ignore the FILENAME statement. However, the SAS log indicates that the files are created or that they are not found, as shown in these examples:
filename fred 'c:\sastest\newdata2.xlsb';
proc export outfile=fred
dbms=excelcs
data=sasuser.baseball replace;
sheet='Hello';
run;
NOTE: "Hello" range/sheet was successfully created.
NOTE: PROCEDURE EXPORT used (Total process time):
real time 0.76 seconds
cpu time 0.12 seconds
When using the filename with the IMPORT procedure, you receive the following message:
ERROR: Unable to open file FRED. It does not exist or it is already opened
exclusively by another user, or you need permission to view its data.
To circumvent this problem, use the full path in the OUTFILE= parameter for EXPORT and DATAFILE= parameter for IMPORT, as shown here:
proc export outfile='c:\sastest\newdata2.xlsb'
dbms=excelcs
data=sasuser.baseball replace;
sheet='Hello';
run;
proc import datafile='c:\sastest\newdata2.xlsb'
dbms=excelcs
out=baseball replace;
sheet='Hello';
run;
Operating System and Release Information
SAS System | SAS/ACCESS Interface to PC Files | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M0 | |
Microsoft Windows XP 64-bit Edition | 9.2 TS2M0 | |
Microsoft® Windows® for x64 | 9.2 TS2M0 | |
Microsoft Windows Server 2003 for x64 | 9.2 TS2M0 | |
Microsoft Windows Server 2008 for x64 | 9.2 TS2M0 | |
Windows Vista | 9.2 TS2M0 | |
Windows Vista for x64 | 9.2 TS2M0 | |
64-bit Enabled AIX | 9.2 TS2M0 | |
64-bit Enabled HP-UX | 9.2 TS2M0 | |
64-bit Enabled Solaris | 9.2 TS2M0 | |
HP-UX IPF | 9.2 TS2M0 | |
Linux | 9.2 TS2M0 | |
Linux for x64 | 9.2 TS2M0 | |
Solaris for x64 | 9.2 TS2M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2013-03-01 16:43:35 |
Date Created: | 2010-08-16 12:08:26 |