About ChrisHemedinger

ChrisHemedinger · ‎05-14-2007

Brian, EG 4.1 does not support the Drillthrough Action. It does support standard drillthrough to detail, though. Chris

ChrisHemedinger · ‎04-25-2007

Musaddaq, This sounds like an issue for tech support. You can begin a track by using: http://support.sas.com/techsup/contact/submit_emits2.html Chris

ChrisHemedinger · ‎04-23-2007

If you are fairly certain that you've removed Enterprise Guide but Add/Remove Programs doesn't seem convinced, you can try removing this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{E0E662A9-EDC9-4C8B-9E84-448646810926} Note that this is for Enterprise Guide 4.1. All of the usual disclaimers/warnings about editing your registry apply -- be careful! Chris

ChrisHemedinger · ‎04-09-2007

Mike, You bring the Diet Coke, Mentos, and a mop, and I'll see what I can do. 🙂 Chris

ChrisHemedinger · ‎04-09-2007

Currently the best way to do that within EG is to first use the query builder to create a filtered data set (can be a table or view), and then use that as input into your Summary Tables task. Chris

ChrisHemedinger · ‎04-09-2007

Trying to explain it to your friends? Try pointing them to the new "sascom voices" blog, especially this entry: http://blogs.sas.com/sascom/index.php?/archives/21-Why-Im-not-in-marketing.html Chris

ChrisHemedinger · ‎04-09-2007

The next version of Enterprise Guide (4.2) will support .NET 2.0. That version will be available with SAS 9.2. Unfortunately, I'm not in a position to publish dates for availability -- all I can tell you is that we're working on it. If you attend SAS Global Forum next week you'll be able to see a preview of these releases. Chris

ChrisHemedinger · ‎04-04-2007

Henk, The answer is in this thread: http://support.sas.com/forums/thread.jspa?messageID=2296 Short answer is that you cannot easily use VS2005 to create custom tasks for EG 4.1, because the version of .NET is different. EG requires 1.1, and VS2005 targets .NET 2.0. Chris

ChrisHemedinger · ‎04-03-2007

Are you attending SAS Global Forum this year? Want to hear what SAS and your peers have to share about EG? Some of the SAS presentations include: Extending SAS Enterprise Guide and SAS Add-In for Microsoft Office with Custom Tasks The Next Generation of Desktop Business Intelligence- SAS Enterprise Guide and the SAS Add-In for Microsoft Office The New World of SAS: Programming with SAS Enterprise Guide Hands-On Workshop: SAS® Business Intelligence Applications Empowering Your SAS® Business Intelligence End Users via a SAS® Stored Process Integrated Reporting Using SAS®9 BI Clients There are also many presentations offered by fellow SAS users, including these titles: Creating Custom Add-ins for SAS Enterprise Guide and the SAS Add-in for Microsoft Office Dynamic Projects in SAS® Enterprise Guide® – How to Create and Use Parameters A "SAS® Programmer's" Guide to SAS® Enterprise Guide® Point-and-Click Style Editing in SAS® Enterprise Guide® SAS® Enterprise Guide® and Stored Processes SAS/CONNECT to Mainframes and Servers in SAS Enterprise Guide 4 Using SAS Code Data on Demand with SAS® Enterprise Guide®: A Cheap and Easy Approach to Real-Time Database Access Creating ActiveX Graphs for Presentations Using SAS® Enterprise Guide® and Drill-Down Graphs Too Benchmarking Sub-Annual Series to Annual Totals – From Concepts to SAS® Procedure and SAS® Enterprise Guide® Custom Task And more! Search http://support.sas.com/events/sasglobalforum/2007/index.html for more titles and topics, and plan your conference accordingly. We'll also be in the SAS demo room to meet you and answer any questions you have, plus gather your feedback. Stop by and say hello! Chris

ChrisHemedinger · ‎03-28-2007

Try using the FILENAME statement with the MOD option to append an existing output file. For example, in your first code node you might have something like this: [pre] filename mytext "c:\temp\out.txt"; ods listing file=mytext; proc print data=sashelp.class; run; ods listing close; [/pre] Your next code node could have this: [pre] filename mytext "c:\temp\out.txt" mod; ods listing file=mytext; proc print data=sashelp.air; run; ods listing close; [/pre] As a result, you should find that "out.txt" contains the results from both programs. Chris

ChrisHemedinger · ‎03-23-2007

From the message, it seems that the text file resides on a remote SAS server. Is that correct? The message indicates that EG cannot read the contents of the file, because in order to read the file it would have to transfer it from the remote server to your local server. That operation would be expensive because the file is so large, so EG "skips" that step. If you have access to the file from your PC, say on a network share or mapped drive, then EG should be able to preview the contents of the file. Simply select "Local Computer" instead of "SAS Servers" when selecting the data file. Chris

ChrisHemedinger · ‎03-21-2007

I think we need more information about how you are importing this. Are you using the Import Task in Enterprise Guide, importing as Fixed Width text file? Otherwise, this might be a good question for tech support folks: http://support.sas.com/techsup/contact/submit_emits2.html Chris

ChrisHemedinger · ‎03-21-2007

You might try clearing the footnote with a FOOTNOTE; statement. PROC COMPARE seems to write directly to the LISTING destination when a footnote is active. Chris

ChrisHemedinger · ‎03-12-2007

Tim, Currently, the only way to create custom tasks is to use our .NET APIs -- that means Visual Studio for most folks. In the future we might try to make this process easier for folks who simply want to surface their parameterized SAS programs, similar to a stored process. But there are no concrete plans yet. I invite you to submit your suggestion via the tech support page. Chris

ChrisHemedinger · ‎03-01-2007

If you are talking about the Files location you see when you expand a server (SASMain, for example), and see Libraries and Files... The Files location shows the file system of the SAS workspace server host. The starting location for that file navigation is controlled by the SAS server definition in SAS Management Console. There are instructions in this SAS Note for how to change that: http://support.sas.com/techsup/unotes/SN/016/016364.html If you are talking about the "SAS Folders" that hold BI content such as Stored Processes and Information Maps, then you can control that view by using the BI Manager in SAS Management Console. Chris

Online Status	Online
Date Last Visited	44 seconds ago