OK. I'll try. I set tools --> options --> results --> results general to RTF, and tools --> options --> results --> graph to ActiveX (that the default). When I run a task with graphics, it looks great on the screen and in Word when I e-mail it to myself. But when I e-mail it to my colleagues/clients, the graphs are gone. Bill said to go to tools --> options --> results --> graph, and send the clients the SAS ActiveX Control that is there. So I added this to my outgoing e-mail message (matches my version of SAS host): "To view the graphics, you need to execute this ActiveX control (just once per PC). http://www2.sas.com/codebase/graph/v91/sasgraph.exe" Now they can see and print the graphics. This is a PC-only solution; no Mac's. One nagging piece is that I don't know how to make the graphics "static" so I can send them to journals and slide-shows. Doc ... View more

Bill, in Tech Support, had the answer. "In order to display an ActiveX SAS/Graph image the end user will need to download the ActiveX graph control just once. You can point the user to the path using the same path your EG session is pointing too...Tools > Options > Results > Graph.", so I included the web link in my e-mail message from EGuide. ... View more

Think about this. As the SET statement is executable, you could read the coefficients, retain them for th DATA step, and then drop the variables from the output dataset; this is done once. You could have a second SET statement to read in the nObs dataset. * untested code; DATA scored; IF _N_=1 then SET Coefficients; RETAIN Var1-Var9; DROP Var1-Var9; SET NObs; Predicted = Var1 + Var2*VarA + Var9*VarX ; RUN; ... View more

I'm confused by this question. EG is a client tool and doesn't seem to use all that much memory. BI is a different product and is off-topic for this forum. ... View more

I think that you jsut need to remove the single quotes (') from the work.score in the out= parameter. doc ... View more

To compare data set attributes, youo coul dyse PROC COMPARE and tell it to suppress the record-level comparisons. You could also use PROC CONTENTS and output the data structure and then use PROC COMPARE on the results. Doc ... View more

Josh, In "SAS for Dummies", Chris was referring to using the "Local Computer" vs "SAS server" to get the data. If you are bringing in data from the "local computer", EGuide has to read the data and then send it off to the SAS server for processing (it may be read 2 or more times to accomplish one task and may have to traverse a small pipe). If you use the "SAS Server", then 1) the data are already in a SAS dataset (or linked to a database) and 2) the "SAS Server" accesses the data directly, without any EGuide client involvement. Depending on what you are trying to do and your hardware environment, one method could be superior to another or vice-versa. There is no universally applicable answer to your question. Doc ... View more

Matt, With your experience in SAS coding, you might want to get a couple of Books-by-Users. "SAS for Dummies" is a quick read and shows how the pieces of SAS are wrapped up in EGuide. "SAS Programming for Enterprise Guide Users" shows how to incorporate the coding tools you know into the EGuide environment. EGuide does it's basic data transformations using PROC SQL. If you've never used SQL (and many scientist users haven't), it's worth learning. Doc ... View more

Josh, I'm not sure where you are going with this question, but I'll give it a go. The server configuration files are in SASV9.CFG, but it's location is dependent on installation parameters that you set. You can just search for the file name. Some configuration parameters can also be set in AUTOEXEC.SAS and on the SAS command execution. The SAS execution log for any EGuide task is located with the task. Just right-click on the task in the process flow. To my knowledge, nothing that is SAS-specific goes in the system logs (the use of the SAS program itself might be there, but nothing about how it was used). Doc ... View more

One caution. All of these responses are looking at duplicate keys (BY-variables). You may weed out RECORDS that are not duplicates. The only way to truly get at all duplicate records is to use all the variables as keys. ... View more

Chuck, You could also add the Unix commands that you need to your Windows box. There is freeware available that include more, less and tail (Google: ) or you could just buy the fancy version from MKS Toolkits. The 0K .log size problem that you mentioned earlier happens in Unix too. SAS writes the log in blocks (and the block-size is system dependent, based on disk utilization), so what you see as the 'end' is not necessarily 'current.' Doc ... View more

There is. It's described in the SAS system concepts help. SAS dates go back to sometime in the 1572, the start of the Gregorian calendar. ... View more

Karen, This is where the statistician has to play 20-questions with the requestor. They are doing an audit. For what purpose? What are they trying to show? Is budget a consideration? The answers to all those questions will help guide the sample size. I wouldn't necessarily consider the population to be fixed and finite. The population size may be conceptually infinite (the audit is for the calls done for this month, but if you want to generalize, the population is the calls that could ever have been made.) If this is an audit for QC, then looking at some of the SAS/QC tools can help (Shewhart and Pareto charts may be useful). Doc Muhlbaier Duke ... View more

Tech support is the place. Since you have a clear error message, my first approach is to go to the tech support web site (support.sas.com) and search for "enterprise guide" " " as "enterprise guide" "could not connect to server" That approach can get you a long way to self support (especially late at night), and back to doing the task at hand. ... View more