Hi, @ballardw: I agree with you. There's something in the code or in the style template or maybe even in Word that is adding the dotted border. When I test using either the defaults or with a custom template, I do not get any dotted line. Cynthia ... View more

Hi:   When I take ALL the defaults for ODS RTF (default style) and ODS RTF TEXT= (default colors), I do not observe any dotted lines.   Are you by any chance using a custom style template to alter the presentation of the ODS RTF TEXT= element? It is unlikely that a default style template would be changing the TEXT= color or font because you have to explicitly change the UserText element in order to change what is there. And, even when I apply a changed template to alter the UserText element, I don't see a dotted line: (I made the Word doc at 200% to see whether there was a dotted line.)   You might want to work with Tech Support on this. They can look at ALL your code and your template (assuming there is one) and help you figure out what is happening.   Cynthia   ... View more

Hi:   We recommend that you refer to the documentation to find whether an option for a procedure is required to be specified a certain way. Here are 3 different invocations of PROC SORT. Note that all 3 invocations work, even if the options like DATA=, OUT=, DUPOUT= and NODUPKEY are listed in a different order each time:   Generally, after the keyword PROC you must list the procedure name and then usually other options can be specified in any order. As a best practice, I always use the DATA= option and the OUT= option first, when I code my PROC SORT, but even DATA= is optional because if you don't have it, then SAS uses the value of the automatic variable _LAST_.   Cynthia ... View more

Hi:   As noted, it is unlikely that many people will open a zip file. Without seeing your code, it's hard to guess what you mean. There are 2 scenarios with PROC REPORT that come quickly  to mind, however, using Spanning Headers in a COLUMN statement or using ACROSS items. In either case, you see an empty cell sometimes, as shown below: I don't know if this is what you're describing, but it is not possible in PROC REPORT syntax to "merge" the cells vertically in order to get rid of the empty cell above either Name (first example) or Region (second example). You could fiddle around and change the border colors to try and make it appear as though there was just one cell -- it would still be 2 separate cells though. And depending on your destination, that may or may not work to fiddle with the border colors.   You can do both row spanning and column spanning with the Report Writing Interface as shown in this paper https://support.sas.com/resources/papers/proceedings16/SAS5762-2016.pdf on page 19, you can see how vertical spanning is produced for the Overall CSS column. You'd have to use a similar technique if this is the type of thing you want to do.   Cynthia ... View more

Hi: This may be a question for Tech Support. A few questions that may help you debug the issue: 1) if you send a single email from your system to the receivers system (not using a program -- just using the COMPOSE function of your email system), do they get the email? 2) has the receiver checked their mail application to see whether the programmatically sent mail was misdirected to their junk or spam folder? 3) if you send mail from your program to an address that does NOT contain an ampersand, does the receiver get this mail? 4) Are you sure that all of your system options related to email are correct? Other than running those tests to get some more context on the scope of the issue, I think your best option for resolving this is for you to open a track with SAS Tech Support. Cynthia ... View more

Hi: I believe that link was the original 9.1 link when the ODS RTF features were still experimantal -- like BODYTITLE, etc. All of those features are now production. So even though the link is broken, my guess is that the "experimental" page was removed when all the features were made production. Cynthia ... View more

Hi, @Tom: That's correct; however the original posting showed HTML output not LISTING, and the code showed no change to the SPLIT= option, so the default was in effect. I haven't had a chance to test the original code in EG yet, but I suspect it won't make a difference. Thanks for the clarification. Cynthia ... View more

Hi:   The WHERE statement is  not a global statement. Here's the page for Global Statements: https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lestmtsglobal/n0e7kamd4b486zn10o4lcseg4qvd.htm      WHERE is a flexible statement, documented in the DATA step syntax, https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lestmtsref/n1xbr9r0s9veq0n137iftzxq4g7e.htm#n0gcjivvzd7mown1nghhoukvf56l  but with the extra information that it can be used with any procedure that reads data: In the context of the program for that activity, I would consider WHERE to be a statement that "belongs" to PROC PRINT syntax in that example, in a way that is different from the TITLE statement or other GLOBAL statements. The WHERE statement has to be used somewhere -- inside a DATA step or a PROC STEP. The WHERE statement can't be used in the same way that a TITLE, FOOTNOTE, OPTIONS or other global statement can be used.   But you're right, to a certain extent, this is splitting hairs. Yes, one of the goals was to have the student recognize that the RUN; ends the PROC PRINT and the PROC MEANS and the DATA step in this activity. But one of the other goals was to have them recognize that the TITLE statements are GLOBAL statements that do not need a RUN;   Cynthia ... View more

Hi:   Question 3 in that same activity is going to ask students about Global statements. That's where they can count the TITLE statement. The point of this activity is to get the students to identify global versus regular statements and to recognize step boundaries.   My take on your thought exercise, if the TITLE statement were inside the PROC PRINT, I would say that there are still 4 PROC PRINT statements and 1 global statement that has been placed INSIDE the PROC PRINT step. But, in the activity program, we want the students to start learning how to read the program -- how to identify the steps, how to identify step boundaries and global statements.   The lecture immediately before that activity is explaining SAS program structure and what a program "step" is. The lecture covers how a "step" is composed of statements and typically ends with a RUN or QUIT statement. The lecture explains that a SAS program can also contain global statements (like TITLE or FOOTNOTE or LIBNAME,etc) which do not end with a RUN or QUIT.   The program for the activity looks like this (I've added the color coding):     But why bother with the emphasis on global statements at all? What if the PROC PRINT statement was as you coded it, but there was not any TITLE statement before the PROC MEANS? A new SAS programmer might not expect these results from the changed program:   The TITLE statement is still a GLOBAL statement whether it is placed inside or outside of the PROC step where it is used. One of the reasons our programs always show the TITLE and FOOTNOTE statements placed immediately BEFORE the PROC statement in our starter programs is so students get into the habit of thinking first about the global statements, such as OPTIONS, LIBNAME and TITLE and FOOTNOTE, that their steps will need to have in effect before the step runs. Cynthia ... View more

Hi: I typically do not open Microsoft documents. However, although I'm not sure I understand your first question, the second question about changing the view is something that typically happens when the zoom level on your browser is set to something too high, so that the list of videos and the display screen no longer fit side by side. Usually, this happens to me when I switch from my desktop (with a large monitor) to my laptop, with a smaller screen. I notice that when I change the browser zoom level on my laptop, the e-learning courses don't display the same side-by-side way that they do on the desktop. I have to return the zoom level to somewhere between 90-100% in order to have everything "fit". Hope this helps. Cynthia ... View more