@SAS_V_R wrote:
Tom, the machine I am using is my work computer. What other machine could it be?
Enterprise Guide is a front end tool for creating and submitting SAS code. It does NOT actually run SAS code itself. For it to be able to run SAS code it has to connect to a copy of SAS. It could be connecting to a version of PC SAS that is installed on your work PC, in which case then PROC EXPORT can write to any disk on that PC.
But normally people use Enterprise Guide to run SAS on some server. Typically that server is running Unix and not Windows (although there are some strange shops that do run SAS on a Windows Server machine). So unless there is network drive where you can write the CSV file that is accessible to both the SAS server and your PC you will probably have to copy the CSV file to be able to load it into SQL server.
Can you share exactly what buttons you are pushing in Enterprise guide to EXPORT the file? Which menus, which choices you made etc.
If instead you ran some SAS code that resulted in EG giving you that error then show the SAS code. It might be that you have accidentally made EG think that the CSV file is a result that want to download and view on your PC. Like the output of a PROC GLM call or something. I think there are options in EG to tell to not try to open the outputs. Or perhaps tricks to make the output so that EG does not consider it as something you want to view. But I don't really use EG.
These are the export options: xlsx
xls
mbd
text files csv
text files txt
text files tab delimited tab
text files space delimited txt
All html files
sas data files sas7bdat
I used text files comma delimited csv
Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!
Check out this tutorial series to learn how to build your own steps in SAS Studio.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.