About ChrisHemedinger

ChrisHemedinger · ‎10-04-2006

Hi, This doesn't sound like correct behavior. My advice is to try applying the EG 4.1 hotfix (see previous post) -- it does address a handful of Import Data scenarios. However, I reviewed the fix list and your symptom doesn't stand out; nor have we been able to reproduce this here with the information you've provided. If the hotfix doesn't solve it, please contact SAS tech support with the details. Chris

ChrisHemedinger · ‎10-03-2006

There is a new resource for statistics students and professors (and anyone with an interest) -- if you've wondered how to start using SAS Enterprise Guide for your applied statistics analysis, this is the guide for you. Here is a link: http://support.sas.com/training/elearn/statlibrary/ Click on the "Learn How with SAS" section, and prepare yourself for a very impressive and interactive tour. Enjoy, Chris

ChrisHemedinger · ‎10-03-2006

There is a new hotfix available for EG 4.1 -- it addresses several customer-reported issues, a few of which have been mentioned on this forum. The link: http://ftp.sas.com/techsup/download/hotfix/ent_guide41.html Chris

ChrisHemedinger · ‎09-22-2006

Hi, See this thread: http://support.sas.com/forums/thread.jspa?forumID=10&threadID=585&tstart=0 Chris

ChrisHemedinger · ‎09-20-2006

Hi, Currently there isn't a way to specify the profile (metadata repository) to use at start up. In EG 4.1 you can use Tools->Options->Security options to select not to store metadata credentials in your local profile, and thus see a prompt each time you launch EG. However, that's useful in your case only if your various metadata profiles differ only by user ID/password, not by host and port settings. Chris

ChrisHemedinger · ‎09-15-2006

Linda, That's a new addition for EG 4.1. You should work with your SAS support folks to get an upgrade! Chris

ChrisHemedinger · ‎09-15-2006

In EG 4.1 you can use Project Parameters to create a parameter as a placeholder for a variable name in a task. (Tools->Parameter Manager, then define a new parameter of type Variable). Most SAS tasks will then accept that parameter as a value you can assign in the task's roles page. However, if you are looking to check for a condition and execute one set of PROC code versus another depending on the value of the condition, that's not something that EG will facilitate via point and click. But you certainly can write your SAS program in EG and then convert it to a stored process. You can even use project parameters to parameterize your program in EG, so that you are prompted for the condition values as you run it. The project parameters are then translated into stored process parameters automatically. Chris

ChrisHemedinger · ‎09-11-2006

Hi, EGAuto.sas is a hook that we sometimes suggest for customers to insert custom code that must be submitted upon connection to a server. However, it isn't really captured in the project flow when you export SAS code. Other hooks include the custom code items in Tools->Options (insert code before/after tasks, SAS programs). That code is exported as part of the flow. Chris

ChrisHemedinger · ‎09-07-2006

Right-click on the flow in the Project Explorer and select Schedule . That will interface with the Windows Scheduler and create a script file to automate EG to run. Chris

ChrisHemedinger · ‎09-07-2006

Richard, I don't think the icon has anything to do with it. You can debug this yourself via Visual Studio -- attach the debugger to the SEGUide process and see where the exception is thrown. You might need to contact tech support on this -- they would follow up probably by asking for your add-in file and possibly the VS project, and then we could better diagnose it. Chris

ChrisHemedinger · ‎09-07-2006

Kenny, I'm afraid not. EG forces the banner image to be centered. The only suggestion I can offer is to increase the width of the image file to the right with white space, thus the pretty part of the image will appear more to the left when viewed in a browser. Chris

ChrisHemedinger · ‎09-07-2006

Lee, For EG 4.1 you want to use this prog ID: Set objApplication = CreateObject("SASEGObjectModel.Application.4") You can get a quick example by going to Tools->Schedule Project. This will bring up the Windows scheduler dialog, which you can cancel. Then you'll have a VBScript file referenced in your project that performs a simple automation task of running the project. Chris

ChrisHemedinger · ‎08-30-2006

Maurice, You need to convert your numbers to strings using the InvariantCulture format provider. For example: double myDouble = 4.25; string value = myDouble.ToString(System.Globalization.CultureInfo.InvariantCulture); That will prevent the French culture settings from influencing the text value. Chris

ChrisHemedinger · ‎08-30-2006

I'd suggest that you contact tech support for this issue. You should also supply an example SAS program for what you're seeing. http://support.sas.com/techsup/contact/submit_emits2.html Chris

ChrisHemedinger · ‎08-29-2006

Lee, Sounds like you would like to write code similar to the following: Public Sub foo() Dim objApp As SASEGScripting.Application Dim objProject As SASEGScripting.Project objApp = New SASEGScripting.Application objProject = objApp.Open("myproject.egp", "") objProject.Run End Sub This is an example of "early binding" code, which requires a reference to the EG scripting model exposed via COM. Most of our examples to date use VBScript and the "late binding" model, where you have a CreateObject("SASEGScripting.Application") call. Requires no COM reference, but the IDE doesn't help you with intellisense and such. The SASEGScripting.dll is a .NET DLL, but it does expose a COM model. However, the type library required isn't registered by default. Here's how you can register it. 1. Open a command prompt window. 2. Run this command: (paths may vary depending on your installation) c:\WINNT\Microsoft.NET\Framework\v1.1.4322\RegAsm.exe /tlb:SASEGScripting.tlb /codebase "c:\Program Files\SAS\Enterprise Guide 4\SASEGScripting.dll" Expected response: Microsoft (R) .NET Framework Assembly Registration Utility 1.1.4322.573 Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Types registered successfully Assembly exported to 'c:\Program Files\SAS\Enterprise Guide 4\SASEGScripting.tlb', and the type library was registered successfully 3. Run this command: (paths may vary depending on your installation) "c:\Program Files\SAS\Shared Files\Integration Technologies\RegTypeLib.exe" "c:\Program Files\SAS\Enterprise Guide 4\SASEGScripting.tlb" Expected response: Registered c:\Program Files\SAS\Enterprise Guide 4\SASEGScripting.tlb 4. After these steps are completed, you should be able to Insert a reference to SAS Enterprise Guide 4.1 Object Library from your VBA application. Chris

Online Status	Offline
Date Last Visited	10 hours ago