About CaseySmith

CaseySmith · ‎04-23-2019

That is correct. Microsoft fixed this issue in their Windows 10 April 2018 Update (version 1803), so you would have to be on that Windows 10 version (1803) or later to get the fix. However, I do not know if there is a bulletin or KB article associated with the specific fix. Casey

CaseySmith · ‎04-23-2019

It is still on our list for future consideration, but no, it has not been implemented yet, and will not be in our next release (EG 8.1). Casey

CaseySmith · ‎04-22-2019

Hi Uday, See http://support.sas.com/kb/59/828.html... Many SAS administrators have to reference more than one path where folders or files do not exist within the same subdirectory; examples follow: C:\public\sasdata C:\users\sales Because the File Navigation tab options can accept only a single path, create symbolic links to the directories in question. For the above example, create symbolic links to both sasdata and sales in a single directory. Then refer to this single directory path in the Specify Path field on the File Navigation tab. That SAS Note also points out that environment variables can be used on Windows servers... Note: If your SAS Workspace Server is running on a Windows server, you can use an environment variable. However, the variable must come first in the path and must begin with an exclamation point. For example, to use the USERPROFILE environment variable, you can use the following path: !USERPROFILE\your-subfolder\ As another example, you might be able to use the USERNAME Windows environment variable in the server file navigation path to start each user in their respective sub-directory (if their usernames match the subdirectory names). Casey

CaseySmith · ‎04-04-2019

The standalone installer is still an option for deploying the SAS Add-in for Microsoft Office (and SAS Enterprise Guide) when it comes with your order, but for technical reasons, it does not come with all orders that include the SAS Add-in for Microsoft Office. Specifically, it comes with orders that also include the SAS Web Parts for Sharepoint (BIWEBPTSMSSP). For example, it comes with Office Analytics. Casey

CaseySmith · ‎04-03-2019

Did you record the response file when you deployed on a system that already had 7.12 installed (like your users) or on a system with no SAS products installed? If the latter, I'd try the former, since there are different dialogs and required responses when the installer goes into update mode. Casey

CaseySmith · ‎04-03-2019

Hi @DDutton, Not all operations can be executed (thus recorded) as commands in a macro. The two operations you provided (saving and selection via *mouse*) are examples. You can see a full list of the commands supported in a macro by clicking Program > Editor Macros > Macros, then click the Create button. You'll notice there are quite a few selection commands (a whole category). If you perform selections via the keyboard rather than the mouse while recording a macro, they will be recorded and can be replayed in a macro. Casey

CaseySmith · ‎04-03-2019

That is correct. SAS Studio does not currently open ODS results generated by hand-written ODS statements in your code. We hope to support this in the future. For now, if you create hand-written ODS results, you'll have to navigate to the location you created the ODS results file and explicitly open it. Casey

CaseySmith · ‎03-25-2019

There is not currently a way to customize the appearance of the EG data grid. Are you mainly wanting a different background color for just the column and row headers? Or are you wanting subtle alternating background colors for each row? Or something else? In EG 8.1 (coming out later this year), there is a dark theme that might help: EG 8.1 also picks up Windows High Contrast themes better than previous releases. Casey

CaseySmith · ‎03-22-2019

Here is a similar thread: https://communities.sas.com/t5/SAS-Enterprise-Guide/Making-EG-Stop-Executing-subsequent-process-flows-based-on-a/m-p/313292/highlight/true#M21132 In it, I point out the project option that you can use to stop subsequent execution when an error is encountered, though I haven't explicitly tried it with ordered lists. Casey

CaseySmith · ‎03-15-2019

Thanks for the feedback. We are planning to generate very similar wrapper code (including the macro variables) in SAS Studio and EG in future releases. Casey

CaseySmith · ‎03-14-2019

Hi @RosemaryM, The EG (and AMO) standalone installers do not currently handle this well. As you noted, the shared components are not uninstalled. I won't bore you with the technical reason, but I can say that we have plans to address this in the future (by way of full MSI installers for the product and all its dependencies). In the meantime, if full uninstall cleanup is a requirement, a 3rd-party tool is probably the best way to accomplish. One example is Revo Uninstaller. Also, I believe traditional deployment (the SAS Deployment Wizard) handles this better than the standalone installer, so you could try it instead. Casey

CaseySmith · ‎03-14-2019

Hi @Edoedoedo, The current plan is for SAS Studio 5.2 to be available near the end of this year, but the date is not set in stone. I am not able to reproduce the unresponsiveness working with a large program in SAS Studio 5.1. I opened three large SAS programs (32107, 7123, and 6566 lines) and had no delay when editing each. Sorry you are experiencing poor performance. It would be good to report this to SAS Tech Support to see if they can help diagnose, and so they have a record in case others are experiencing. In the meantime, SAS Studio 4.4 is available with SAS Studio 5.1 deployments. Thank you for the feedback. Casey

CaseySmith · ‎03-13-2019

Hi Tommaso, We have identified some performance issues related to working with tables in SAS Studio 5.1 (StudioV), which have been improved in our next SAS Studio release (5.2). Also, SAS Studio 5.1 (StudioV) uses SAS Viya microservices to do its work, while SAS Studio 4.4 uses a more direct connection, which contributes at least some of the difference in performance. We are continuing to optimize performance, but in the meantime, there may be scenarios where it is more performant to use SAS Studio 4.4 instead. Casey

CaseySmith · ‎03-12-2019

Hi Tom, I highly recommend trying the SwitcherUtility.exe tool (in your AMO installation directory; ex. C:\Program Files (x86)\SASHome\x86\SASAddinforMicrosoftOffice\7.1) to get the SAS Add-in for Microsoft Office loading again. (I'd certainly try that before re-installing.) It is typically used to switch between versions of the add-in (when you have more than one version installed), however it re-registers the add-in, which usually fixes up problems with it not appearing. Here is a screenshot of the utility: Note: Make sure you run it as an administrator, since it needs permission to update the Windows registry for it to be able to register the add-in. If that doesn't do the trick, @TimBeese should be able to get you going again. Casey

CaseySmith · ‎03-11-2019

@Sk4r, no worries... See the last two paragraphs in this blog entry for instructions on how to change the registered SAS command (includes link to a tool for convenience, as an alternative to manually editing your registry): https://blogs.sas.com/content/sasdummy/2009/11/19/using-the-x-and-systask-commands-from-sas-enterprise-guide/ Or if you want to do it manually, here are the typical locations the registered SAS command lives in your Windows Registry (the ones from my machine): 32-bit: HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{20001C16-05D1-4706-9BD2-1782B8575063}\LocalServer32 HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{20001C16-05D1-4706-9BD2-1782B8575063}\LocalServer32 HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{440196D4-90F0-11D0-9F41-00A024BB830C}\LocalServer32 HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{CF7BC7E6-C7E8-11D5-87E3-00C04F38F9F6}\LocalServer32 HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{E251B1BF-8E46-4CBE-AD83-6389185bA373}\LocalServer32 HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{081d5c22-7b63-433a-9a65-12a8d276bcc9}\LocalServer32 HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{20001C16-05D1-4706-9BD2-1782B8575063}\LocalServer32 64-bit: HKEY_CLASSES_ROOT\CLSID\{20001C16-05D1-4706-9BD2-1782B8575063}\LocalServer32 HKEY_CLASSES_ROOT\CLSID\{20001C16-05D1-4706-9BD2-1782B8575063}\LocalServer32 HKEY_CLASSES_ROOT\CLSID\{440196D4-90F0-11D0-9F41-00A024BB830C}\LocalServer32 HKEY_CLASSES_ROOT\CLSID\{CF7BC7E6-C7E8-11D5-87E3-00C04F38F9F6}\LocalServer32 HKEY_CLASSES_ROOT\CLSID\{E251B1BF-8E46-4CBE-AD83-6389185bA373}\LocalServer32 If you navigate to those keys, you'll see the registered SAS command with the "-noprngetlist" option on the end. (Or you can search your registry for "noprngetlist", which should locate the keys.) Note: If you want to re-register your SAS command at any time (to get back to default), you can do so via "C:\Program Files\SASHome\SASFoundation\9.4\sas.exe /regserver" command. Casey

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