Hi, You should contact tech support with this issue. But here is something to check... As a user of EG 3, did you define a library in the EG administrator to redirect your default output location to EGTASK? If so, you might try using the SAS Enterprise Guide Explorer (off of the Tools menu) to delete and redefine that library. Another test you can do first: try changing the settings for Tools->Options->Tasks: Output Library to put WORK at the top of the list instead of EGTASK, and then try creating a query. If it works, then try the above step of deleting/redefining EGTASK. Chris ... View more

John, The Clsid property returns a value called a GUID, which you can generate easily from a Visual Studio command prompt. Simply run "uuidgen", and it will generate one for you -- copy and paste it into your task code. The Visual Studio templates that we provide (for VS2003) will generate the value for you. If you are developing a task without using the templates, you'll have to use uuidgen. It's important to supply a unique value for the Clsid for each task. This value is how Enterprise Guide can distinguish one task from another. If you have two or more tasks with the same Clsid value in your \Custom directory, Enterprise Guide will show only the first one it finds. Chris ... View more

Steve, I'd suggest sending this information to tech support ( http://support.sas.com/techsup/contact/submit_emits2.html ). They can ask the right questions and provide some advice to solve your problem quickly. Chris ... View more

If you are using a shared EG repository, it is possible for an admin to control who sees which tasks. This is described in the admin guide linked from http://support.sas.com/eguide . However, if you are using a SAS metadata repository (for SAS 9 integration), then this administration feature is not available. This is planned for support in a future release of SAS Enterprise Guide. Chris ... View more

Louis, When EG3 submits a job to SAS, it "listens" for events from the SAS server that indicate an error. Occasionally SAS triggers an error event that doesn't correspond to an error in the resulting SAS log. In this case, I think you can consider the error indication as erroneous -- or at least not important for your output. EG 4.1 fixes this by actually examining the SAS log for error lines and displaying the dreaded "red X" only when the log actually contains an error. Chris ... View more

HP, Okay, put on your sunglasses -- here comes the light! Enterprise Guide is a client application to SAS. Its main charter is to make SAS easy to use, but it relies on SAS to do all of the heavy lifting for data management, reporting, and analytics. So most work that you do in Enterprise Guide is represented in SAS programs that Enterprise Guide generates on your behalf. For SAS programs to run with your data, your data must be accessible to the SAS server that is doing the processing. If you use Enterprise Guide to select local data from your PC to analyze, then Enterprise Guide does you the great favor of moving your data to a remote server, when necessary, in order to provide SAS with access to it. If you have small data files, you probably won't even notice this transition. But large data files (and I consider 1GB large) would introduce a noticable delay. For this reason, it would be better for you to define access to your data relative to the SAS server. That means defining a SAS library that resolves to the location where your data is located, and then accessing that data via the SAS library instead of via the local PC file system. Chris ... View more

HP, You can easily use local SAS data sets with EG. If your configuration is SAS for Windows and EG installed on your personal machine, then there is virtually no administration necessary. If you and your 10 colleagues share a central SAS server, all connecting to that server via EG, then there is a bit of administration necessary to configure that. However, even that process is pretty straightforward, and you can still use your local SAS data sets (EG will move them to the remote machine as needed). Chris ... View more

Here is the VB.NET version of this function: Public Function get_SasCode() As String Dim member As String = IIf((Me.bAllMembers OrElse (Me.dataset.Length = 0)), "_ALL_", Me.dataset) Dim co As String = Me.catobs.ToString Dim macro As String = Global.ReadFileFromAssembly("EGAddin.CharacterizeData.Characterize_Data.sas") Dim call As String = String.Format("%charact(dsn={0},lib={1},catobs={2});", member, Me.library, co) Dim charts As String = IIf(Me.bCharts, Global.ReadFileFromAssembly("EGAddin.CharacterizeData.GraphCode.sas"), "") Return macro & Environment.NewLine & call & Environment.NewLine & charts End Function Great places to start with .NET development: http://www.gotdotnet.com (Microsoft-supported community) http://www.codeproject.com Chris ... View more

John, Most custom tasks simply generate SAS code based on user selections in one or more forms presented in the task. When you already have a SAS macro that does the work you want, the only variation in the generated code from run to run is the parameters passed to the macro, or else perhaps some %LET statements to set up some variables. You're not calling the macro directly from the task; you are simply generating a SAS program that will call the macro when run within EG. Is there a C# example that we have that looks like what you want to do? If so, post back and I'll try to provide some code snippets for a VB.NET equivalent. One other note: if you are using VS2005, you'll want to look at this thread: http://support.sas.com/forums/thread.jspa?forumID=10&threadID=121&tstart=0 Chris ... View more

Wim, In this case it's the behavior of the META engine that is getting in your way. The META engine is the library engine that looks into metadata for library and table definitions. Prior to SAS 9.1.3 SP 4, the META engine really wants to update table metadata when you create tables. However, it requires that you first drop tables of the same name before creating new ones. When you do that, the table object in metadata winds up being a new, different table object (even if the contents are the same). With Service Pack 4 of SAS, the META engine changes behavior so that it does not update metadata. If you want to add tables to the library, you should assign the library with the METAOUT=DATA option, and then sync the library contents in metadata by using PROC METALIB (added with Service Pack 3 of SAS). EG 4.1 facilitates the METAOUT=DATA option with its library definition dialogs in the Tools->SAS Enterprise Guide Explorer. You will still need to run the PROC METALIB step yourself to sync the table definition in metadata. More information about PROC METALIB: http://support.sas.com/documentation/onlinedoc/91pdf/sasdoc_913/omd_ref_8969.pdf Chris ... View more

Not currently, no. Those three you mentioned are the options for exporting data as text files. Chris ... View more

In order to define least squares effects, you must: 1. On the Task Roles page, assign at least one variable to the Classification role 2. On the Model page, add the classification variable as an Effect. 3. On the Post Hoc Tests->Least Squares page, click Add -- it will add the classification variable as the selected effect. If you have more than one classification variable assigned as an effect, then you can select among them. Hint: the task window does show some helpful messages in the status bar, providing cues as to what is required to use the controls on this page. Chris ... View more

It means that another SAS session has the data set open. Since this is in SASUSER, it must be a SAS session that you were using previously, perhaps via a different EG session. If this is a local SAS install on your PC, check Windows Task Manager for extra SAS.EXE sessions that might be running. One of these SAS sessions might be locking your data set file. Chris ... View more

Autosave is a popular request and we are considering it for a future release. In the meantime, Ctl+S is the keyboard shortcut in EG 4.1 to save the project file. Ctl+Shift+S is the keyboard shortcut to save the "current document" (for example, a SAS program that is saved external to the project). Chris ... View more

Andreas, Thanks for trying to stretch EG with custom tasks! We have considered implementing something just like what you've suggested, but we didn't get it done in time for EG 4.1. We'll have it on the list for consideration for a future release. Thanks, Chris ... View more