![]() NOTE: The file DDECMD is: DDE Session, SESSIONexcelsystem,RECFMV,LRECL256 NOTE: 1 record was written to the file DDECMD. NOTE: The SAS System stopped processing this step because of errors. It will, though, always be in the same folder as the SAS file. ERROR: Physical file does not exist, excelsystem. I do not want to have to hard-code the path to the CSV file, because this will vary depending on who is exporting the data, and where they decide to store it. Instead of finding the CSV file in the same folder, it is looking in the Windows\System32 folder (which is not where it is).Ĭ:\WINDOWS\system32\DATA_E XPORT_2008 -04-29.CSV. Infile 'DATA_EXPORT_.CS V' delimiter = ',' MISSOVER DSD lrecl=32767 firstobs=1 If you have not transferred the file created by PROC CPORT in binary format, PROC CIMPORT cannot read the file, and you receive the following message: ERROR: Given transport file is bad. However, even though the syntax file does not specify a specific path for the CSV file: ERROR: Physical file does not exist, C:\SAS\SASCAT.DAT. This should pull in all the data from the associated DATA_EXPORT_.CSV file, complete with labels, formats, etc. The instructions are to double-click the DATA_EXPORT_.SAS file (syntax file) to open that file in SAS. ![]() I am using a web-based application that creates 2 data export files for pulling data into SAS:īoth of these files are saved together in a folder (the folder can be anywhere).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |