Hi!  When you say "in my views", exactly which UI features of EG are you referring to?  The Query Builder?  Filter and Sort?  The data grid?  I ran this code in EG 7.11 (with EG display language set to Swedish): data blah; infile datalines dsd; input color $; datalines; Ljusröd Mörkröd ; run; And then used the resultant data set in the Query Builder and in Filter and Sort, and the values displayed as expected in the UI: Also, submit this to see what your server locale and encoding options are set to: proc options group=languagecontrol; run; ... View more

That feature was removed in the EG 7.1 data grid (no way to turn it on), but we do plan to add it back in the next release. ... View more

You cannot use DDE from EG (which connects to "headless" SAS sessions), since DDE relies on Windows messages and requires the SAS session to run in a windowing environment (and on the same machine as the process it is communicating with). However, you can run VBSCript from EG if X commands are allowed on your server.  For example: /* write the vbs file */ data _null_; file 'c:\temp\test.vbs'; put "Set objFSO=CreateObject(""Scripting.FileSystemObject"")"; put "outFile=""c:\temp\test.txt"""; put "Set objFile = objFSO.CreateTextFile(outFile,True)"; put "objFile.Write ""test string"" & vbCrLf"; put "objFile.Close"; run; /* execute the vbs file */ X 'c:\temp\test.vbs'; ... View more

I can reproduce it pretty easily by submitting the following code to create a value with a long length (3000 in this case), then hover over that value in the data grid (over RDP (presentation virtualization, similar to Citrix) -- haven't tried directly logged into the client machine yet): data blah; x="012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789"; run; The problem (delay/unresponsiveness) appears to get worse the longer the value. I doubt there is currently a way to prevent the problem other than avoiding hovering the mouse over very long character values in the data grid, so the tooltip will not attempt to be rendered.  However, I will enter this in our tracking system so we can investigate a fix for a future release. ... View more

Hi David, I think your best bet to resolve will be to open a ticket with Technical Support...  Technical Support Form.  They will need additional details. Casey ... View more

Hi Dmitry, Currently, no, there is not a way to specify the maximum number of output data sets for each task.  However, if there are output data sets you do not want added to the project/process flow, you can write them to a temp library, unassign the library at the end of your task/program code, and they will not get added to the project.  For example: libname blah 'c:\temp'; data addToProject; x=1; run; data blah.doNotAddToProject; x=1; run; libname blah clear; In this example, the first data set (addToProject) will get added to the project, but the second data set (doNotAddToProject) will not. Casey ... View more

There is not currently a way to set the label of a program node in EG programmatically via SAS code.  However, you could set it programmatically using EG's automation/scripting interface.  Attaching a VBScript code example that will do it.  (Technically, you could write out the VBScript file and execute it (if ALLOWXCMD) using SAS code, but the VBScript would be what actually interfaces with the EG automation API and changes the name of the program element.) (Note: If you open a .sas file in EG, the label of the program node in EG will match the file name, and it cannot be changed.) ... View more

The intent of that message is to warn the user that even though an item is referenced in multiple ordered lists, it will only be run the first time it is encountered in a run (rather than re-run for each occurrence). However, it should only be displayed when the user is running multiple ordered lists that contain multiple references to one or more items.  EG should not be displaying that warning when the project is saved.  I'll enter a defect into our tracking system and make sure it is addressed. ... View more

pchegoor wrote: Casey Smith    Thanks for the explanation of the UPDATE feature  in SAS EG 7.11 . I  still wonder why SAS had to release SAS EG 7.11 instead of incorporating these features in let's say SAS EG 8.1 .  But now with this new UPDATE feature , can we expect that Future versions of SAS EG can be downloaded as part of the UPDATE feature including Major releases ? .Of course one needs to be aware of Project incompatibility in such a case. We are exploring the possibility of being able to deliver any updates (hotfixes and major releases) via the "Check for Updates" feature, but there are challenges to work out.  I would not say you can "expect" to see this in a future release, but that we are exploring the possibility. Also are the below the only new features available with SAS EG 7.11 or is there more to it?  I am guessing a Project creating in SAS EG 7.11 will be incompatible with a project created with SAS EG 7.1 Can you please confirm this? The features listed are the primary new features and enhancements for 7.11 (and of course, there are always a number of bug fixes with every release).  We chose the version number to be 7.11, because it is a relatively minor release (more like an update to 7.1).  As such, we also ensured projects would be reasonably compatible between 7.1 and 7.11 -- a project created in 7.11 can be opened in 7.1 and vice versa.. ... View more

Actually, we did not add a role capability for "Check for Updates" because role capabilities are only honored if you are connected to a profile (metadata server). Role capabilities serve primarily as UI customization, rather than security.  For example, if you switch to no profile, then all features are available. We added a config file option that can be set to hide the "Check for Updates" feature, regardless of what profile you are set to.  Also, admin can deny the functionality (ability to download and/or run the installer) at the OS level. ... View more

Hi Michelle, The "Check for Updates" feature is currently for minor updates/hot fixes (what you can download manually from the Hot fix pages on the SAS support site), which will not impact project compatibility.  However, we are considering the possibility of also using for major updates in the future, and you are correct, we would have to address project compatibility.  Btw, there are several ways for an admin to disable and hide the "Check for Updates" feature, if they do not want end users to have access to that feature. Casey ... View more

This VBScript code below from the blog link below slightly modified to run the EG project worked for me.  It triggers specifically when a file is added to a folder, but I imagine it could be altered to listen for file modification instead. (Note: EGScript1.vbs is the vbs file created when you schedule a project from within EG.) ' See http://blogs.technet.com/b/heyscriptingguy/archive/2004/10/11/how-can-i-automatically-run-a-script-any-time-a-file-is-added-to-a-folder.aspx ' Save as and run FileSystemWatcher.vbs and it'll start a wscript.exe process strComputer = "." Set objWMIService = GetObject("winmgmts:" _     & "{impersonationLevel=impersonate}!\\" & _         strComputer & "\root\cimv2") Set colMonitoredEvents = objWMIService.ExecNotificationQuery _     ("SELECT * FROM __InstanceCreationEvent WITHIN 10 WHERE " _         & "Targetinstance ISA 'CIM_DirectoryContainsFile' and " _             & "TargetInstance.GroupComponent= " _                 & "'Win32_Directory.Name=""c:\\\\scripts""'") Do     Set objLatestEvent = colMonitoredEvents.NextEvent     Wscript.Echo objLatestEvent.TargetInstance.PartComponent 'Run the EG project Dim objShell Set objShell = Wscript.CreateObject("WScript.Shell") objShell.Run "C:\Users\cassmi\Desktop\EGScript1.vbs" ' Using Set is mandatory Set objShell = Nothing Loop ... View more

Ha ha, thanks Chris!  I did realize shortly after posting, my announcement was rather dry.  I'm sure we'll see more cool highlights on your SAS Dummy blog! ... View more