Hi, PIPE, SYSTASK and XCMD are among the features disabled by default when running a SAS server configured with SAS Integration Technologies. These features can present a risk to use on a central server that is accessed by lots of users with Enterprise Guide. By default, the Object Spawner starts the SAS session with the -NOXCMD option which does not allow SYSTASK commands to be run. I'd suggest opening a track with tech support and explaining your situation; they can advise you as to the best workaround for what you're trying to do. Chris ... View more

The short answer is that EG submits a few macro definitions at startup aimed to help with some SAS features, such as creating accessible graphs. See http://support.sas.com/techsup/unotes/SN/018/018103.html for more information and possible resolution. Chris ... View more

Winnie, This is the result of some overzealous anti-spyware. See: http://support.sas.com/techsup/unotes/SN/013/013349.html Chris ... View more

Ted, You can do this with the query builder in EG. 1. Add both tables to the query builder. (Let's call them TABLE1 and TABLE2). Add the desired columns to the "select" list. 2. In the Join window, make sure that the tables are joined on the key column you want. (Ex: TABLE1.column and TABLE2.column) 3. Modify the Join type to Outer Join (last selection in the list of join types) That specifies that you want all rows from both tables to be considered for the result set. Now you want to create a filter so that you get only those rows with a value in the first table and NOT in the second table. So... 4. Create a filter: where TABLE2.column IS NULL ("IS NULL" is a selection in the filter operator list) That should get you what you want. Chris ... View more

Rob, You didn't say what version you are using, but the double-prompt behavior you describe was a problem in EG 3.0, and is resolved in EG 4.1. The automation prompting behavior is also improved in EG 4.1. Chris ... View more

Robert, Yes, EG 2.0 and 4.1 can coexist. The error you see looks like an incomplete installation. You might be able to repair it by: 1. Open a command prompt at your EG 4.1 installation directory. 2. Run "seguide /register" Chris ... View more

Jouni, If you haven't already, please make sure that you contact tech support about this issue. As we prepare a future fix for this and any other reported problems, we would like to make sure that it fixes your scenario. Chris ... View more

You might need to set the fmtsearch option within your stored process program to ensure that the stored process session can access your defined formats. Chris ... View more

Hi, You didn't say whether you are using the Forecast Studio Open Project wizard within SAS Add-In for Office. Are you? You should be able to open a hierarchical project from there. Chris ... View more

If your libraries are defined in metadata, you might need to tag them as "preassigned". See this SAS note: http://support.sas.com/techsup/unotes/SN/014/014080.html Enterprise Guide 4.1, combined with SAS 9.1.3 SP4, improves the experience quite a bit. Chris ... View more

To make sure I've got this straight: you have EG on your local PC and SAS on a central Windows server that you connect to via Citrix. Correct? EG connects to remote machines via Integration Technologies. To connect EG to that SAS server, you must set up Integration Technologies on the server, with a running object spawner to listen for connections. You must also define that connection in a metadata repository (can be your local repository, or using the SAS Metadata server). You would do this using either SAS Management Console or Tools->Options->SAS Enterprise Guide Explorer in EG. Once you've got that connection established, you can access your ODBC data sources as you do now: via SAS libraries within your SAS session. Chris ... View more

I'm taking a guess here, but I suspect that there are some oracle-enabling environment variables that are not being set when you run your SAS command. When you run within EG, EG connects to a SAS session that is launched by the object spawner. The object spawner launches a SAS command that is, most likely, wrapped up in a shell script that sets some environment variables so that your SAS session can act as an Oracle client. You'll probably want to contact tech support for help in figuring this one out. Chris ... View more

Winnie, Yes, you can set the option in Tools->Options->Data: General. It's "Use data tables in unprotected (read/write) mode". If you check the option, EG will automatically attempt to open tables in "update" mode when you add/open them in your project. The treatment applies to all tables, not just those generated by your task. I suspect you might find this isn't the behavior you want in general, but you can try it for yourself. Chris ... View more

In your class you must implement the ISASTaskSubmitSink interface, which has just one method to implement: SubmitComplete. That will provide you with the SAS log and an indication of success. The VB.NET function signature looks like this: Sub SubmitComplete( _ ByVal Cookie As Integer, _ ByVal Success As Boolean, _ ByVal Log As String _ ) Chris ... View more

Check out the How To resources at: http://support.sas.com/training/elearn/statlibrary It may have exactly what you're looking for with an example of the Mixed Models task. Chris ... View more