Hi,   I am currently working at a site with SAS Enterprise Guide 7.1 under 9.4.   I have noticed that when using the Data Grid to view my datasets, I can no longer freeze column or rows, or hide columns or rows.   I am sure that I am missing something very fundamental here, but under previous EG versions, when I right-mouse click on a column header in the Data Grid I get a context menu that includes the following items:   Hide Show Hold Free   Currently I am not seeing any of these items in the context menu and, for the work I am doing, I really need the functionality that these menu items offer.   I had wondered if this was related to Roles and Capabilities provided to my Profile, but with my friendly SAS Admin we have tried to find an Enterprise Guide Capability that covers this menu but we have been stumped.   I have seen a few screenshots of SAS EG 7.1 Data Grids in my research for this problem and am getting a little nervy that these menu items and this functionality may have been dropped from this version.   Please would some kind person allay my fears and show me how I can get that Data Grid working for me again.   Many thanks,   Downunder Dave, Wellington ... View more

Hi, (Using SAS 9.3 (TS1M1) via SAS Enterprise Guide 5.100.0.12019) (64-bit) on Windows 7 Pro) I would like make use of a user defined PICTURE format to form the column labels in a bar chart. I want my columns to be labelled in <yyyy>-<mm> format, such as 2014-07 for any event occurring in Jul-2014. However, when I run PROC GChart out to any of main ODS destinations and using any Graph Format setting (ActiveX, PNG, GIF etc.), the results are not what I expected. For example, when using ODS destination of HTML and Graph Format of ActiveX, my chart shows a single column with a label that looks like this snippet shows: Just one big column, where I expected one column per <yyyy>-<mm> combination in my data, and, the label is simply the text of the directives comprising my PICTURE format, whereas I was hoping for 2014-07, 2014-08, 2014-09 etc. However, when I run the same code out to the ODS SAS Report destination, I get three columns, which is great, but the columns are labelled like this snippet shows, which is not so great: The SASLOG shows a single warning as: WARNING: The intervals on the axis labeled SalesDate are not evenly spaced. however, in this case I do not think that this is material. There is a currently unanswered SAS Communities posting that raises similar behaviour but that was concerning the Graph Template Language () , whereas this is bog standard SAS and Proc GChart and the trail went cold on that other posting in 2011. I have put together a simple set of SAS code to show the definition of the PICTURE format, proof that the format works OK when used to format a value in the SASLOG with a PUT statement and then the Proc GChart code that I am using. If anyone can spot what I am doing wrong here I would appreciate some assistance. I know that there are a million workarounds for using dates in SAS/Graph, but in this case I know that it should work and I want to keep my date values as proper date values, not convert them to character. My sample code is shown below. The two FORMAT statements in the final Proc CGhart can be flipped around to show that, when using a built-in SAS format (YYMON8.), the columns group correctly and are labelled correctly. However using the user-defined PICTURE format DATE_GROUPING. the columns do not behave as I expected them to. Cheers, Downunder Dave Welllington. Options LINESIZE=145; *********************************************************************************; *Create a custom Picture format to represent date values as <yyyy>-<mm>          ; *e.g. 2014-07 for any date falling in July 2014.                                 ; *********************************************************************************; Proc Format Library=WORK; Picture Date_Grouping Low-High= '%Y-%0m' (DataType=DATE); Run; *********************************************************************************; *Prove that it works with some sample data....                                   ; *********************************************************************************; Data Sales_Details; Input SalesDate    Date9.; Put SalesDate=Date9. SalesDate=Date_Grouping9.; Datalines; 04Jul2014 13Jul2014 28Aug2014 11Aug2014 15Aug2014 06Sep2014 06Sep2014 06Sep2014 ; Run; *********************************************************************************; *Create a simple bar chart.                                                      ; *********************************************************************************; Axis1 STYLE=1 WIDTH=1 MINOR= (NUMBER=1); Axis2 STYLE=1 WIDTH=1; Title1 "Sales Bar Chart"; Proc GChart Data=Work.Sales_Details;     VBAR SalesDate / CLIPREF FRAME    DISCRETE TYPE=FREQ COUTLINE=BLACK RAXIS=AXIS1 MAXIS=AXIS2; /*    Format    SalesDate YYMON8.;*/     Format    SalesDate Date_Grouping9.; Run; ... View more

Under SAS/EG 4.1 I can display several datasets simultaneously by right mouse clicking each dataset's tab and choosing [New HorizontaTab]. A child window is opened which can accept other datasets as well. Generally I can have about three or four datasets open in separate child windows. I do not seem to be able to do this in SAS/EG 4.2. The best I can do is change the Workspace Layout to Stacked, but that seems to be limited to a maximum of two windows at any one time. Does anyone have a clever trick to overcome this? Cheers, Downunder Dave. ... View more

I am using SAS Enterprise Guide 4.1 (4.1.0.471) and want to be able to use the Filter & Query task to summarise my data using an existing user-defined format to group my values. As an example, my demo data looks like this: Data Transactions; Input Cust_No Trans_Code ; Datalines; 555 1 555 1 330 2 630 2 777 2 805 3 658 4 ; Run; My demo format looks like this: Proc Format Library=WORK; Value Trans_Code 1,2 = "Purchases" 3,4,5,6,7,9 = "Cash Advances" Other = "Unknown" ; Run; when hand-coding (ie writing SAS code myself) I can use either of the following techniques: 1) Use Proc Summary with a Format statement to group by the Trans_Code variable after being passed through the format Trans_Code. Proc Summary Data=Transactions NWAY missing; Class Trans_Code; Format Trans_Code Trans_Code.; Output Out=SummaryA(Drop=_TYPE_ Rename=(_FREQ_=NumberOfRows)) ; Run; 2) Use Proc SQL with a Put function to group Trans_Code values by the format, Trans_Code. Proc SQL; Create Table SummaryB As Select Put(Trans_Code, Trans_Code.) As GroupTranscode, Count(*) As NumberOfRows From Transactions Group By Calculated GroupTranscode ; Quit; However, I need to be able to do this same grouping from the Filter & Query task , ie without writing code. I realise that the Recode A Column feature of the Calculated Column option can produce the same results as I require, but having to hand-build the rules for re-coding a column each time is not practical. In my real data, there are many hundreds of discreet Trans_Code values and the SAS format that we have built reduces these down to about 50 groups. Does anyone know how we can use the Filter & Query Task to do the above. The only way I can think of doing it is to build a Calculated Column with the Expression Builder and build an expression as: Put(Trans_Code, Trans_Code.) I wonder if I am missing something a bit more obvious that is buried in the Filter & Query Task somwhere. Any thoughts, anyone ? Many thanks, Down-under-Dave Wellington New Zealand ... View more

Hi, With SAS/Enterprise Guide 4.1 running SAS on a Windows server we experience numerous occasions where one user might be browsing a SAS dataset (in the default read-only mode) and another user needs to run some code to update that same dataset. By having the dataset open in browse mode, the first user is preventing the second user from being able to update the dataset. The second user receives the following message: ERROR: A lock is not available for BANANA.SHOES_DAVE.DATA, lock held by another process. Whilst it is annoying that the read-only mode is not actually read-only, we would really like to be able to identify which user has a particular dataset open so that we can contact that user and ask them to close the dataset in question. We have several hundred users and, at present, are only able to send an eMail to all users to ask them to check to see if they have the dataset open. Does anyone know a way that we can identify the user or the session ID that has the dataset open in browse mode. There does not seem to be a .lck file created for this situation as there is when user #1 is updating the dataset themsleves, perhaps with a Proc Sort. I had thought that the LOCK statement would help identify the user with the dataset open but apparently not. Any thoughts or clever ideas? Whilst it would be nice if the solution was within SAS, we could live with a DOS/Windows workaround. Cheers, Down Under Dave ... View more