My work laptop had a hard drive failure recently, and I was issued a new one. Along with upgrading me to Windows 11, I was given an upgrade from SAS EG 7.2 to 8.3. For the most part, it's going fine, but I've got two issues that I haven't been able to find a solution for:   1) The browser-style tabs at the top of the main window that list your open, active files--is there a way to get rid of that? I've found the controls for almost everything else--I even managed to wrangle the new log setup into something I'm comfortable with--but I can't find anything that touches that, and it's both unnecessary (I use the project display, which so far serves the exact same purpose in a much more readable way), and regularly causing me to click on the wrong thing and confuse myself (ie, I go to click back to my code from the results or log display, and instead end up in an entirely different code file).   2) The behavior of the run button. My instinct, from previous versions of EG, is to use F8 to run a selected portion of code and the run button to run an entire file. But 8.3 defaults the run button to "run selected", it seems, and I haven't seen the option to change that.   Thank you in advance for any advice! ... View more

I'm trying to add a column with a manual title to an already existing proc report. However, when I add the code to the column line, the resulting report puts all of the new data in the title rows rather than the table, then fills the table cells in with 1. Here's my code:   data test; input col1 $ col2 $ col3 $ col4 $ col5 $ @@ ; datalines; foo bar foo bar foo bar foo bar foo foo foo bar foo bar foo ; proc report data=test spanrows nowd style(header)={bordertopwidth=.5 borderbottomwidth=.5 borderleftwidth=.5 borderrightwidth=.5 borderstyle=solid bordercolor=black}; column ('Overall' (("Group 1" (col1 col2)) ("Group 2" (col3 col4)) ("Group 3" (col5)) )); define col1 / " " style(column)={width=100%}; define col2 / " " style(column)={width=100%}; define col3 / " " style(column)={width=100%}; define col4 / " " style(column)={width=100%}; define col5 / " " across style(column)={width=100% vjust=m just=c tagattr='wrap:yes'}; run; The result I'm getting is this: What I'm looking for is Group 3 to be on the same row as Group 1 and Group 2, and 'foo' to be in the cells where the 1s are. As far as I can tell, my column statement is nested properly, and messing with the the final group doesn't seem to change anything. What am I missing? ... View more

I have the following piece of code that works fine as a standalone pull:   proc sql; connect to teradata (authdomain='LDAP_auth' SERVER= teramed1 mode = teradata); create table test as select * from connection to teradata ( select sub_ed.eci, sub_ed.hh_episode_bgn,count(sub_ed.incurred_dt) as ed_during_ct , min(incurred_dt) as ed_during_dt from sudd02a.hh_3_ed sub_ed left join sudd02a.hh_1_episodes sub_ep on sub_ed.eci = sub_ep.eci and sub_ed.hh_episode_bgn = sub_ep.hh_episode_bgn group by 1,2 where sub_ed.incurred_dt between sub_ed.hh_episode_bgn and sub_ep.hh_episode_end); quit; However, when I wrap the select statement into a left join as part of a much larger pull from Teradata     left join (select sub_ed.eci, sub_ed.hh_episode_bgn , count(sub_ed.incurred_dt) as ed_during_ct , min(incurred_dt) as ed_during_dt from sudd02a.hh_3_ed sub_ed left join sudd02a.hh_1_episodes sub_ep on sub_ed.eci = sub_ep.eci and sub_ed.hh_episode_bgn = sub_ep.hh_episode_bgn group by 1,2 where sub_ed.incurred_dt between sub_ed.hh_episode_bgn and sub_ep.hh_episode_end) ed2 on ep.eci=ed2.eci and ep.hh_episode_bgn=ed2.hh_episode_bgn Enterprise Guide throws the error:   ERROR: Teradata prepare: Datatype Mismatch in THEN/ELSE expression.   I can't figure out what might be causing that error. It's not the ON variables: there's a join just above this one that uses the exact same tables and variables, and it works fine.    ... View more

So I'm seeing something odd when trying to play with cell borders in a proc report going to an ODS EXCEL output. The client is requesting that some of the cells be merged horizontally--as far as I can tell, I can't do that via SAS, but I figured I could try and fake it with 0-width internal cell borders. This seems to work fine in the internal results viewer, but when transitioned to Excel, any cell with any border attribute defined instead gets completely surrounded.   SAS EG results viewer:   Excel output:   Desired Excel Output:   And my code: ods excel file="&PDFPath./&&filename_value._&&qvar..xlsx" style=journal options(embedded_titles='yes' embedded_footnotes='yes' sheet_interval='NONE' sheet_name="&qtrvar. Summary" absolute_column_width='26,12,26,12' ); proc report data=source spanrows nowd style(header)={bordertopwidth=.5 borderbottomwidth=.5 borderleftwidth=.5 borderrightwidth=.5 borderstyle=solid bordercolor=black}; column ("Level 2" (row1 value1 row2 value2)); define row2 / " " style(column)={width=1000%}; define row1 / " " style(column)={width=1000% bordertopwidth=.5 borderbottomwidth=.5 borderleftwidth=.5 borderrightwidth=.5 borderstyle=solid bordercolor=black}; define value1 / " " style(column)={width=1000% bordertopwidth=.5 borderbottomwidth=.5 borderleftwidth=.5 borderrightwidth=.5 borderstyle=solid bordercolor=black}; define value2 / " " style(column)={width=1000% bordertopwidth=0 borderbottomwidth=0 borderleftwidth=0 borderrightwidth=.5 borderstyle=solid bordercolor=black}; compute value1; if row1 = 'Target Achieved: Y' then do; call define('row1', 'style', 'style=[background=lightgreen font_weight=bold just=c]'); call define('value1', 'style', 'style=[background=lightgreen font_weight=bold just=c]'); call define('row2', 'style', 'style=[borderbottomwidth=.5]'); call define('value2', 'style', 'style=[borderbottomwidth=.5]'); end; else if row1 = 'Target Achieved: N' then do; call define('row1', 'style', 'style=[background=lightred font_weight=bold just=c]'); call define('value1', 'style', 'style=[background=lightred font_weight=bold just=c]'); call define('row2', 'style', 'style=[borderbottomwidth=.5]'); call define('value2', 'style', 'style=[borderbottomwidth=.5]'); end; endcomp; quit; ods excel close;   ... View more

I'm creating a report that's meant to go out to some of our clients, based on an excel mockup I was given, and I've mostly managed to recreate what I'm being asked for. However, I've hit a (minor, admittedly) stumbling block.   The data I'm working with is currently structured as follows:   a b c d text1 num1 text2 num2 ... etc   and the proc report is written:   proc report data=base; column ("Header1" (("Subhead1" (a b)) ("Subhead2" (c d)))); define a / " " style(column)={width=1000%}; define b / " " style(column)={width=1000%}; define c / " " style(column)={width=1000%}; define d / " " style(column)={width=1000%}; quit;   which produces:   Header1 Subhead1 Subhead2 text1 num1 text2 num2 ... etc   The stumbling block I've hit is that they've asked that "Header1" be conditionally colored based on some of the values in the data. Changing the style(header) backgroundcolor attribute hits both the header and the subheads, so that won't work. First question, then--is there a more specific attribute that would only hit that Header1 row?   If not (which I suspect is the case) the idea I had was to restructure the data so that the Subheads were instead grouping or across variables. When I tried this, however, I got some unexpected results.   New data structure:   Group a b Subhead1 text1 num1 Subhead1 ... etc Subhead2 text2 num2 Subhead2 ... etc   New proc report:   proc report data=base2; column ("Header1" (groups (a b))); define groups / " " style(column)={width=1000%}; define a / " " style(column)={width=1000%}; define b / " " style(column)={width=1000%}; quit;   which resulted in:   Header1 Subhead1 text1 num1 ... etc Subhead2 text2 num2 ... etc   I then tried changing groups to an across variable in the definition step,   proc report data=base2; column ("Header1" (groups (a b))); define groups / " " across; define a / " " style(column)={width=1000%}; define b / " " style(column)={width=1000%}; quit; and got the following:   Header1 Subhead1 Subhead2     1   text1 num1 1 ...etc   1 text2 num2   1 ...etc   which is not what I expected. So, second question: What am I doing wrong here, and how do I fix it?   I'm using SAS 9.4.5.0, if that affects things. ... View more