11-22-2011 11:28 AM
I have only EG 4.3 on my PC and a remote server. I imagined that I cannot open a local table located in my c:\document and settings because I don't have a local server. But It works, I have the shorcut of the table in my project. I think it uses a Windows API.
But after I use the query builder on this table to check that my SASAPP cannot see this table (because it is located on my C and I can. I don't understand.
the Code submitted by the wizard is the following and we see that my local table is now in my work with a different name !
CREATE TABLE WORK.QUERY_FOR_AIR_SAS7BDAT AS
FROM WORK.air8810 t1;
Do I have to understand that EG execute silently an upload that let it to execute the query ?
Is there something written on that in the documentation ?
Thanks for your help.
11-22-2011 11:36 AM
EGuide is part of a client server architecture in SAS. EGuide itself can do some things (like open files to view and send e-mails as part of the project and these might use your local drive), but it can's run the tasks themselves (almost all of the tasks require the SAS server).
You might be able to map your local C-drive to the server (perhaps with UNC naming), but you will probably need the help of your network support to set that up.
I'm not sure if there is a nicely capsulated summary of what EGuide does itself and what requires the server for the processing.
11-22-2011 11:43 AM
that's right it cannot run a SAS statement without a workspace server. I know it can run some Windows API especially to import the external data and send email.
But my test was simple, I opened via the Files>Open menu, a SAS table and as you can see it executes my query builder on my SASApp based on a table in my work.
11-22-2011 04:55 PM
Yes, EG uploads it on your behalf. A subtle cue when looking at your project -- if the table name is lower case in the process flow, it's probably a file reference to a sas7bdat file (rather than a library reference). Use the Data->Upload task to control the process more. It's also much faster to upload the data this way than to let EG copy the data implicitly.
11-22-2011 05:14 PM
As I'm writing a paper on the different ways to open a data with EG, I was writing the advantages and limits of the use of the FIle > open menu and I imagined that a local table could not queried by a remote server if the server does not see the path of this table. that's consistent when you think of the old principle of SAS/CONNECT.
I was puzzled / gobsmacked when I directly queried the local without to have uploaded it with the Upload wizard (as you can see the snapshot in my first post).
Need further help from the community? Please ask a new question.