About CaseySmith

CaseySmith · ‎09-18-2018

Hi Frank, Actually, "seguide.exe /register" does not appear to be properly exporting and registering the type library (embedded in the SASEGScripting.dll) as I expected. I confirmed it tries to (at least load/register), but was not working for me. I'll have to investigate that separately. So, I had to follow the steps Chris posted to manually export and register, and they worked for me (on 32-bit EG 7.15)... Here is the exact command I used (run in a Windows command prompt as an administrator) (you may have to update it with your EG installation and .NET Framework directory paths): C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /tlb:"C:\Program Files (x86)\SASHome\x86\SASEnterpriseGuide\7.1\SASEGScripting.tlb" /codebase "C:\Program Files (x86)\SASHome\x86\SASEnterpriseGuide\7.1\SASEGScripting.dll" And the output confirming proper export and registration... C:\Windows\system32>C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /tlb:"C:\Program Files (x86)\SASHome\x86\SASEnterpriseGuide\7.1\SASEGScripting.tlb" /codebase "C:\Program Files (x86)\SASHome\x86\SASEnterpriseGuide\7.1\SASEGScripting.dll" Microsoft .NET Framework Assembly Registration Utility version 4.7.2556.0 for Microsoft .NET Framework version 4.7.2556.0 Copyright (C) Microsoft Corporation. All rights reserved. Types registered successfully Assembly exported to 'C:\Program Files (x86)\SASHome\x86\SASEnterpriseGuide\7.1\SASEGScripting.tlb', and the type library was registered successfully Them run Chris' step #3 in the same command window. Here is the exact command I used: "C:\Program Files\SASHome\x86\Integration Technologies\RegTypeLib.exe" "C:\Program Files (x86)\SASHome\x86\SASEnterpriseGuide\7.1\SASEGScripting.tlb" Note: If you have 64-bit EG, use the 64-bit RegTypeLib.exe instead. For example: "C:\Program Files\SASHome\Integration Technologies\RegTypeLib.exe" "C:\Program Files\SASHome\SASEnterpriseGuide\7.1\SASEGScripting.tlb" Then, when I open VBA References in Excel, SASEGScripting appears and can be used... Casey

CaseySmith · ‎09-17-2018

Hi Frank, The EGScripting.dll is installed and registered with Enterprise Guide, so you should not have to explicitly register it (or the tlb) if Enterprise Guide has already been installed on the machine. However, in addition to the other steps in this thread, if needed, you can also re-register the scripting dll by running "seguide.exe /register" (in the EG installation directory) from a command prompt (run as an administrator). Casey

CaseySmith · ‎09-10-2018

Yes, the SAS Note @SASKiwi referenced is the same issue. A fix was pushed to EG 7.13, 7.12 HF1, and 7.11 HF5, so upgrading to one of those versions or later should help. Yes, the fix will help regardless of whether you are using Citrix (you should no longer see the error message, even if another process has the clipboard open; however, while you won't see an error message, if the clipboard is truly locked you will likely be unable to copy/paste -- the clipboard has to be accessible to copy/paste). Casey

CaseySmith · ‎09-10-2018

While I don't have an explanation why EG is unable to load this particular icon (Data Exploration, I suspect) for some folks (I can't reproduce), I can tell from the callstack, confirmed in the code (and agree with @Kurt_Bremser) that while it may prevent the Open dropdown button (folder icon) on the main toolbar from being populated, it should not otherwise prevent EG from working in any way. Casey

CaseySmith · ‎09-05-2018

Glad to hear that exporting the Project Log as a step in the project addresses your need. Just fyi... you can also perform Project Log operations (such as clear, enable/disable, saveas, and email) via automation... https://communities.sas.com/t5/SAS-Enterprise-Guide/Auto-Purge-Project-Log-in-EG/m-p/436983/highlight/true#M28212 Casey

CaseySmith · ‎08-28-2018

John, Your screenshot is showing the General tab. Click the Software tab and you should see the View Initialization Log button. Casey

CaseySmith · ‎08-27-2018

It looks like your EGOptions.xml file (in C:\Users\<userid>\AppData\Roaming\SAS\EnterpriseGuide\7.1\) got corrupted somehow (perhaps the application process did not end cleanly). Close EG, rename or delete your EGOptions.xml file, then re-start EG. Note: Your EG options are stored in the EGOptions.xml file, so if you made any changes in EG's Tools->Options, you'll have to re-make those changes to your options if desired. Here is another post with the same problem and solution: https://communities.sas.com/t5/SAS-Enterprise-Guide/Failure-in-running-EG-7-1/m-p/290024/highlight/true#M19812 Casey

CaseySmith · ‎08-24-2018

John, Sorry, the "%let_EG_WORKSPACEINIT=1;" is actually part of the EG-generated workspace initialization code, not my custom code. It appears to be part of my custom code, because I did not enter a carriage-return/line-feed after my custom code. If I do enter a CRLF after my custom code, then it appears like this in the log: 522 /* Insert custom code after server connection here */ 523 %put &_SASSERVERNAME; 'SASApp' 524 %let _EG_WORKSPACEINIT=1; The _EG_WORKSPACEINIT macro is simply an internal flag EG uses to indicate/check that workspace initialization has taken place. Casey

CaseySmith · ‎08-23-2018

Using _SASSERVERNAME as you described worked for me... (I used EG 7.15, but I'd expect it to work for any version.) -In EG's Tools->Options->SAS Programs, I checked "Submit SAS code when server is connected" and inserted this code: %put &_SASSERVERNAME; -Then, after connecting to my workspace server ("SASApp" in my case), I checked the workspace server initialization log (right-click the server in the Servers view, select Properties, Software tab, then click View Initialization Log button). At the bottom of the log, it properly printed the _SASSERVERNAME... 522 /* Insert custom code after server connection here */ 523 %put &_SASSERVERNAME;%let _EG_WORKSPACEINIT=1; 'SASApp' 524 So, you should be able to use _SASSERVERNAME in conditional logic in your custom workspace initialization code to submit different code for different servers. Casey Note: If you wanted the same code to be submitted for all users (just different code for each server), I'd recommend adding it to different autoexec.sas files on the server and update the server definitions in metadata to use the different autoexecs.

CaseySmith · ‎08-20-2018

Make sure the openfile parameter is in your registered open command as described here: https://communities.sas.com/t5/SAS-Enterprise-Guide/opening-multiple-programs-in-the-same-session/m-p/476604/highlight/true#M30947 Casey

CaseySmith · ‎08-16-2018

Hi Jim, Yeah, there is no way to print (to paper or PDF) that specific diff view (well, other than taking a screenshot), however you should be able to accomplish by configuring a custom diff tool in EG and using it to print the differences. For example... -In EG's Tools->Options->File Comparison, check Use custom file comparison tool and specify a diff tool installed on your computer. (I like WinMerge.) -In your program's History dialog, multi-select (Ctrl+MouseClick) the two versions you wish to compare, then click the Compare button (which will become enabled when you have exactly two versions selected). -Your custom diff tool will open, displaying the differences between the two selected versions. -Click Print in your custom diff tool. Your diff tool will very likely support printing the differences, though it may be in a different display format. (For example, WinMerge displays and prints the differences side-by-side rather than inline +/-.. Git style diff.) I suspect you could find another diff tool that would display the differences in that Git diff layout and use it as your custom file comparison tool in EG. Casey

CaseySmith · ‎08-07-2018

If no libraries are appearing in EG's Server list, then the most likely explanation is that your OBS= system option is set to 0. Thus, the query EG uses to retrieve the libraries returns no results -- can't populate the Servers list. You can confirm this by submitting the code below and inspect the OBS= value in the log: proc options option=obs; run; The most likely reason your OBS= system option is set to 0 is because your server has the SYNTAXCHECK system option turned on and an error was encountered running DATA step code in the server session. In which case, either turn off syntax check mode (NOSYNTAXCHECK) or figure out why the ERROR is occurring and avoid it. See this paper for details on SAS' Syntax Check mode: http://support.sas.com/resources/papers/proceedings13/327-2013.pdf Casey

CaseySmith · ‎08-03-2018

EG's point-and-click Query Builder does not currently support generating "SELECT *" syntax. It currently explicitly lists each column that you select in the Query Builder GUI. So, you can select all the columns in the Query Builder GUI, but the generated SELECT statement will look like "SELECT col1, col2, ..., coln", rather than "SELECT *". Adding explicit support for "SELECT *" to the Query Builder is on our roadmap. It is a reasonable thing to want to do. Thanks for the feedback. Casey

CaseySmith · ‎08-01-2018

@CherylMac, thanks for the additional feedback. We agree, this is painful and needs to be improved. It is on our roadmap. Our current thinking is that we will provide an option that let's users control the initial column widths. The default choice will be "auto-fit", in which EG will automatically set the column widths (up to a maximum size) based on the content (headers and values) in the columns in the initially viewable region. In other words, EG will attempt to fit the column widths to the content by default. The second choice will be "fixed width" columns, in which EG will set the initial width of every column to a value that the user specifies. (Like EG does today, but you will be able to specify the initial size.) Hopefully the two choices provided with this option will address the pain. Let us know if there is another solution you would like to see. For now, the closest you can get is auto-fitting single columns by double-clicking on the separator between column headings, like so... Casey

CaseySmith · ‎07-31-2018

EG's Check for Updates feature queries the xml files from the following locations (depending on version) to determine the latest updates available and where they are located: http://ftp.sas.com/techsup/download/hotfix/HF2/BIRD/eguide_v3.xml (EG 7.13 HF8 and later 7.13, EG 7.15 and later) http://ftp.sas.com/techsup/download/hotfix/HF2/BIRD/eguide_v2.xml (EG 7.11 HF5 and later 7.11, 7.12 HF1 and later 7.12, 7.13 prior to HF8) http://ftp.sas.com/techsup/download/hotfix/HF2/BIRD/eguide_712.xml (EG 7.12 with no hotfix) http://ftp.sas.com/techsup/download/hotfix/HF2/BIRD/eguide.xml (EG 7.11 prior to HF5) However, I would second @Kurt_Bremser's caution for most users, since this is getting into the internals. Casey

Online Status	Offline
Date Last Visited	‎10-09-2025 07:58 AM