Chris Hemedinger’s new book Custom Tasks for SAS® Enterprise Guide® Using Microsoft .NET was recently released. If you have an idea for a really useful additional task you’d like to build for SAS Enterprise Guide, I strongly encou…
Tag: SAS Enterprise Guide
Tracking progress in your program with SAS Enterprise Guide: another trick
I’ve got a new trick that you can use to track progress in a long-running SAS program, while using SAS Enterprise Guide. I’ve previously written about the SYSECHO statement and how you can use it to update the Task Status window with custom messages. SYSECHO is a “global” statement in […]
How to search your SAS Enterprise Guide projects (2013 version)
Last year I published an example application for searching your SAS Enterprise Guide project files (EGP files). The example shows off some of the cool features of the automation API, and it’s a useful tool. As neat of an example as that was, it had some limitations. It worked only […]
SAS Enterprise Guide: 3 Ways to Use the Note Feature
If you look at my desk, my addiction will present itself to you clearly. I love sticky notes – any kind, color, or shape. My bottom desk drawer is full of notepads – some never used because I think they are too pretty to write on. The be…
Controlling access to custom tasks in SAS Enterprise Guide
I’ve bragged about how easy it is to install custom tasks for SAS Enterprise Guide. It’s simple: you copy the .NET assembly (usually a single DLL file) into one of the designated folders in your SAS Enterprise Guide installation, and your task just shows up in the menu. Since I […]
Two awesome Enterprise Guide tricks
Two awesome Enterprise Guide tricks
There and back again: copying files in SAS Enterprise Guide
One of the problems that trips up experienced SAS users when they begin to use SAS Enterprise Guide is a result of simple geography. The SAS Enterprise Guide application runs here, on your desktop. The SAS Workspace session (which accesses data and cranks through your analysis) runs over there, on […]
SAS Stored Process: Benefits of Minimalist Programming
Minimalism SAS stored processes can do a lot. While I haven’t taken on the life of a true minimalist, recently I have come to see the benefits of limiting my stored process source code to just one statement. And the best part of this practice is, I can still do everything I want. When you create a stored process, SAS writes the source code somewhere (see Tricia’s post on where the code is stored). Typically you enter the source code in the stored process wizard. I am now in the habit of typing just one %INCLUDE statement in the source code, and I end up with a stored process window that looks like below. I use the /source2 option to make sure the included code is written to the log. Minimalist Stored Process The full stored process source code ends up as below, because SAS adds a bit of wrapper code: Minimalist Stored Process: Source Code The main code is DoSomething.sas. It has the usual DATA steps, PROC steps, macro calls, maybe even %INCLUDE statements to call other other sub-modules. Minimalist Stored Process: Main Code So what are the benefits? You can store the main SAS code (DoSomething.sas) wherever you want. I’ve been writing SAS code for MUCH […]