Hi @shwms,   Double-clicking a file (ex. .sas) has the same effect as right-clicking it and selecting the Open command on the context menu.  The shell commands for .sas files are located here in the Windows registry:   HKEY_CLASSES_ROOT\SAS.Program.701\shell   The default Open command is located here:   HKEY_CLASSES_ROOT\SAS.Program.701\shell\Open\command   The default value is: "C:\Program Files\SASHome\SASEnterpriseGuide\7.1\SEGuide.exe" /openfile:"%1"   If you want a file to be opened in the same/existing EG session, the command must include the “openfile” parameter, as it is above.  If you want a file to be opened in a new EG session, the command should not include the “openfile” parameter, like so:   "C:\Program Files\SASHome\SASEnterpriseGuide\7.1\SEGuide.exe" "%1"   So, check your Windows registry and make sure that the SEGuide.exe command that is being executed when you double-click the .sas file contains the openfile parameter as in the example above.   Casey   ps- As I alluded to earlier, there can be additional .sas shell commands here in the registry:   HKEY_CLASSES_ROOT\SAS.Program.701\shell   So, if you are using the "Open with..." context menu items, rather than the default Open or double-click, it may be using those associated commands instead.  Check those commands in the registry as well and make sure they are passing the openfile parameter. ... View more

This isn't a complete list, but it checks for many products.   proc product_status can also show what you have installed.   data sasprods; length prodname $ 30 prodcode $ 10 prodmod $ 10 installed $ 12; input prodname 1-30 prodcode prodmod; licensed=sysprod(prodcode); if (prodmod eq '') then installed="<unknown>"; else installed = tslvl(prodmod); cards; Base prodnum0 sasmeans SAS/STAT stat sasglm SAS/GRAPH graph sasgchart SAS/GIS prodnum28 sasgis SAS/ETS ets sasarima SAS/QC qc sascapab SAS/HPF hpf sashpf SAS/AF af sasbld SAS/FSP fsp sasfse SAS/OR prodnum5 sasnlp SAS/IML iml sasiml SAS/Integration Technologies prodnum75 sasiospk SAS/IntrNet prodnum54 sasapsam SAS/SHARE share sasserve SAS/CONNECT prodnum15 saszrlnk SAS/ASSIST assist . SAS/Data Quality prodnum114 sasdqfam SAS/Data Quality Server prodnum256 sasdqfam SAS/Enterprise Miner prodnum102 sasdmine SAS/Text Miner prodnum107 sasemclu SAS/Warehouse Administrator prodnum41 . SAS/ACCESS DB2 (Windows/UNIX) prodnum192 sasiodbu SAS/ACCESS DB2 (Mainframe) prodnum192 sasiodb2 SAS/ACCESS Informix prodnum210 sasionfx SAS/ACCESS Oracle prodnum194 sasora SAS/ACCESS Sybase prodnum204 sassyb SAS/ACCESS PC Files prodnum208 sasdbf SAS/ACCESS ODBC prodnum209 sasioodb SAS/ACCESS OLEDB prodnum215 sasioole SAS/ACCESS R/3 prodnum216 sassr3 SAS/ACCESS SAP BW prodnum221 sassr3 SAS/ACCESS Teradata prodnum219 sastra SAS/MDDB prodnum45 sasmddb Scalable Performance Data Srvr prodnum42 . SAS/SECURE prodnum94 . SAS/SECURE Windows prodnum95 . SAS/Toolkit prodnum16 sasuserp run; ... View more

This worked closer to my problem without the formatting: NOTE.  My field "Hours" was formatted as time5.   So.... data crsefile; set crsefile; hoursdec=timepart(hours)/(60*60); run;   So hours 1:55 became 1.9166666667   ... View more

I don't think haves a wish, more of a concern...? Did some tests as well. My conclusion is when you change table metadata that only resides in the header of the file, the table isn't recreated. This goes for labels, formats and informats. Other changes that changes the structure of the data part of the file will force a recreation of the table. This will include operations such as changing columns length, column type (not available in alter table), adding or dropping columns. When we are at it, for it would seem naturally to have the opportunity to change columns names using alter table. The doc says this can be done using the rename= ds option. But I haven't seen any examples on how to us this together with alter table. My guess that this suggestion has to be used together with create table, or am I missing something obvious...? ... View more

Hi:   Depends on what you want to do and what destinations you have open. I wrote a paper for Global Forum on what I consider to be some common choices for the new behavior. Personally, I turn off the automatic HTML file because I'm too much of a control freak and want to control the name and location of all my output. I don't want it disappearing (as it does in WORK) and I want to know the name. So I always use the "full control" method outlined in the paper. However, other folks might like the automatic HTML file. In this case, an ODS HTML CLOSE; will close that automatic file. You may not want the side effects of closing HTML.   Here's the link to the paper: http://support.sas.com/resources/papers/proceedings12/250-2012.pdf cynthia ... View more

Thanks Everybody.. Even i din't know about the modifier in scan function. ... View more

Here's the word: EG 4.3 will support SAS 9.2 (as it does) and SAS 9.3 (when released). EG 5.1 will support SAS 9.2 and SAS 9.3. Same goes for the SAS Add-In for Microsoft Office (4.3 and 5.1). There are just a few 9.3-specific features that won't work when using the 4.3 versions of these clients. Chris ... View more

Update: I found EGOptions.xml and it appears that it is getting overwritten when EG 4.1 opens. Just for grins and giggles, I tried deleting it and re-creating it, but no luck there, either. ... View more

OK. I just looked at the built-in Help for Enterprise Guide 4.3 and it appears that there IS a topic for Characterize Data in the help index which was not present in Enterprise Guide 4.1. ... View more

Agree with Rob, something like [pre] data _V/view=_V; retain DUMMY ' '; set SASHELP.CLASS; run; ods html style=seaside; proc print data=_V noobs; var NAME ; var DUMMY /style=[background=white foreground=white bordercolor=white cellwidth=900px]; var SEX /style=[just=center bordercolor=#3872AC]; run; ods html close; ... View more

Hi If this is only about subsetting a dataset before you load it into a hash object then why not creating a view and then using this view for loading the hash table, i.e. proc sql; create view HashInput as select from where ; quit; data lookup; set .... if _n_ =1 then do; declare hash h1 (dataset:'HashInput'<,...>); .... end; .... run; If you have to modify the hash table while iterating through the data then look up the add() and delete() methods of the hash object. HTH Patrick ... View more

It's in "%appdata%\SAS\Enterprise Guide\4" (%appdata% resolves to your Windows profile location). Chris ... View more

I recently learned of the capability of Windows 7 to implement a Windows XP machine in virtual mode - EG 4.1 installs flawlessly using the Windows XP Virtual machine. ... View more

There is no built-in version control management in DI Studio. What you can see in the metadata is when the object was changed, and by whom. And if you are lucky, a comment on what was done. What you can do is to either export your job when changed, or use the newly generated SAS program. You could either use an external source code management software, or manually name your programs/exported packages using date-stamps etc. /Linus ... View more