- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Was not sure if this question should be "new users" or SAS EG and If this was asked previously, please supply the link, I couldn't locate an answer
I am trying to determine if you can import Excel without creating a project, when I click on "import data", it states a project must be created first
using SAS EG 8.4 Update 1 (8.4.1.15) (64-bit)
thanks for your assistance,
Lynnette
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
So if the file you want to IMPORT is available on the machine where SAS runs (which can be a different machine than the machine where the Enterprise Guide user interface runs) then you can import it by just writing and running a PROC IMPORT step in the program editor. Make sure to reference the file using the location where it exists on the SAS server, which could look totally different than where the file is visible on the PC that is running Enterprise Guide. Especially if SAS is running on Unix.
But if you want Enterprise Guide to upload the file from the machine it runs on to the machine where the SAS code EG submits for you runs then you will need to make project, even if you throw the project away later.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Projects generate program code.
If you open the program window and type Proc Import code you can run the code.
Or perhaps us a LIBNAME statement pointing at the file to have the sheets treated as data sets. This is often hit or miss because way too many excel workbooks aren't structured well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
@lrpitts64, it's just as @ballardw says.
In EG v8 and later you can open, create, and run SAS program code without a project. Just about every other action (running any task including Import Data or Query Builder) will need the structure of a project, and it will capture that step in the process flow -- even if it's a one-off action that you don't need to save for reuse later.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
So if the file you want to IMPORT is available on the machine where SAS runs (which can be a different machine than the machine where the Enterprise Guide user interface runs) then you can import it by just writing and running a PROC IMPORT step in the program editor. Make sure to reference the file using the location where it exists on the SAS server, which could look totally different than where the file is visible on the PC that is running Enterprise Guide. Especially if SAS is running on Unix.
But if you want Enterprise Guide to upload the file from the machine it runs on to the machine where the SAS code EG submits for you runs then you will need to make project, even if you throw the project away later.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Thank everyone for their quick responses, I really appreciate all your assistance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content