Hi:   Do you mean BODYTITLE vs EMBEDDED_TITLES? I think the EMBEDDED_TITLES is unique to ODS EXCEL. ODS RTF has the BODYTITLE option and ODS WORK has the sub-option BODY_TITLE='ON'. Cynthia ... View more

Hi: The purpose of %put is to write to the SAS log file. Since PROC REPORT is writing to the RTF destination, your %PUT text will never be visible in the RTF file. So I'm not entirely sure what you want to do or where you want your sales figures to be written. The LINE statement is how you write text lines from PROC REPORT. The LINE statement ALWAYS writes output within the boundaries of the PROC REPORT table. So if your PROC REPORT output has borders on the left and right side of the report, the LINE(s) will ALWAYS be written within these boundaries. The other limitation of the LINE statement is that it can ONLY be used in a COMPUTE block that is associated with a break point for an order or group item or associated with the top or bottom of the report (COMPUTE BEFORE, COMPUTE AFTER, COMPUTE BEFORE _PAGE_, COMPUTE AFTER _PAGE_). So if you changed your %PUT to a LINE statement, it would NOT work. The ODS TEXT statement is how you write a text string either before or after a procedure, where the line of text is OUTSIDE the boundaries of the report. So that may be a possibility. In addition, you have 3 macro variables, &sales, &sales1 and &tsales1, but you only show a %LET that creates &sales. So the other values are not going to be found. Cynthia ... View more

A side note-- in order to test the COLUMN_DISPLAY variable in the COMPUTE block for WEIGHT, the best practice is for the COLUMN_DISPLAY variable to be listed on the COLUMN statement in PROC REPORT. Otherwise, you'll get a message like this in the LOG: NOTE: Variable column_display is uninitialized. When worked at a place where I had to turn in my LOG with my REPORTS, notes like this were not allowed because the LOGS were shown to our clients and they would not sign off on a report with a note like this. Cynthia ... View more

Hi: All of these topics -- how to read a CSV file, how to use REPLACE, the difference between the DATA statement and a SET statement and how to use PROC SORT, PROC PRINT, PROC FREQ, and some other basic procedures are all covered in the free Programming 1 class (did I mention it is Free?) You can activate the free class using the Get Started button on this site: https://www.sas.com/en_us/training/offers/free-training.html Cynthia ... View more

Hi: Unfortunately, without data, nobody can run or test your code. Cynthia ... View more

Hi: You do not show all of your ODS statements. Typically, TAGATTR as a style override is used with ODS EXCEL or ODS TAGSETS.EXCELXP. Are you using either of those destinations? I'm curious about why you're using PROTECTSPECIALCHARS=OFF which is most often used when you are inserting raw text into a file like HTML or RTF. Next, you also show listing only options like HEADLINE and HEADSKIP and COLWIDTH which are LISTING only options and ignored by ODS destinations. In addition, without ALL of your code and without any data, if anyone was inclined to help you they would need to guess at what your work.outputw dataset looked like and then they would need to make up some fake data to test their code. Is it possible for you to post some sample data and show ALL of your code so we can see your ODS destination of choice. For example, if you are using ODS EXCEL, I would start by getting rid of the LISTING only options. Cynthia ... View more

Hi: I do not think you can control the formatting using either INDEX="ON" or CONTENTS="YES". I am fairly sure there's not a good way to add big buttons, such as you show in your screen shot. However, you might want to check with Tech Support for the definitive answer. Cynthia ... View more

Hi: Inside the Programming 1 course, there is a lesson entitled "Course Overview and Data Setup". It should be the first section at the top of the course. Assuming you are taking the course on our newest e-learning platform, there is a topic in that lesson on doing the data setup, as shown here:   Note that you will need to follow the instructions for how you are practicing. For example, if you are using the Virtual Lab then the data is already loaded in the Virtual Lab. However, if you are running SAS on your machine, then you must run a program to make the data for class. As you can see in my screen shot, we have multiple sets of instructions for how to make the data. Cynthia ... View more

Hi, At this point, since my code runs correctly, but your code with your data has issues, you might want to consider opening a track with Tech Support. They will need to look at the code/data that works and at the code/data that doesn't work in order to help you find a resolution. Cynthia ... View more

Hi: A similar question has been posted here https://communities.sas.com/t5/SAS-Programming/proc-report-table/m-p/898604#M355186 regarding the insertion of a blank line. As explained in that previous posting, use of options like HEADLINE, HEADSKIP and FLOW are listing only options which will be ignored by ODS destinations like PDF. In addition, as shown in my examples in the other posting, you probably do not need the ASIS=ON style override or the attempt to overcontrol the cellwidths. Cynthia ... View more

Hi: Unfortunately, I'm not sure I understand what you mean. Saying that a value "should" be in the middle of the another value is expressing your desired result. PROC REPORT may not do what you think it "should" or what you want it to do. PROC REPORT considers a break line placed with a COMPUTE block to be a "hard" break. So when you say that a value "should" be positioned "in spite of the blank line" means you want PROC REPORT to do something that it does NOT do. That's not how PROC REPORT operates. You can control the placement of the break line, as I showed when I shifted the break from AGEGRP to DAY. And, shifting the break caused the spanning text for the ORDER items to be shifted accordingly. But the placement of the order variables when using SPANROWS very much depends on the placement of the break line, so the "should" of what you want may or may not be possible given the way that PROC REPORT works. The example below shows the way that PROC REPORT is going to work based on different positioning of the line written in the COMPUTE block. This is how break processing works. When you write a LINE with a COMPUTE block, it will span the entire report table from left side to right side, thus changing the placement of STRAIN and DAY, as shown in my 3 examples above.   This IS the way PROC REPORT will work. What you say it "should" do or what you want it to do is not possible if you continue to put your LINE statement blank line between each AGEGRP value. You may need to investigate the Report Writing Interface with a DATA step program if you need more control over row spanning and column spanning. Cynthia ... View more

Hi:   That's not the way that PROC REPORT works by default. When you have a group or order variable as primary (as you do with strain) and then you have another group or order variable nested within that primary order variable, the values for the primary ordering variable do NOT automatically repeat for each group. You need to control for that yourself, either by making a temporary computed variable that you create. The way that ORDER items work is that the duplicate values are suppressed. So if you really want a blank link under each agegroup unique value and you want the values of strain to repeat, then you'd need to do something more like this: And then, if you wanted to do something similar for the DAY variable, you'd use similar logic. In my example SAVESTRAIN is a PROC REPORT temporary variable whose value is retained automatically. So at the start of every unique value for STRAIN, I "grab" and save the current value in a variable so I can use the value as shown in the COMPUTE blocks. Cynthia . ... View more

Hi:   Using your posted data and simplifying your code and changing the compute block for the blank line and removing the unneeded cellwidth and asis=on specifications and reducing the output to fit on one page, I think this is closer to what you want. I'm still not sure of the purpose or reason behind the need to show 3 dots however, I have highlighted the lines created by changing compute after agegrp to compute after day and then I've also highlighted the one line that was written by compute after strain: SPANROWS seems to be working correctly . Cynthia ... View more