Hi: You don't show all your code or your ODS statements. What is your ODS destination of interest? ODS HTML, RTF, PDF, EXCEL??? Cynthia ... View more

Hi: As a point of interest, PROC SUMMARY and PROC MEANS are very similar procedures. In fact, the PROC SUMMARY documentation points you to PROC MEANS and says that: "The SUMMARY procedure provides data summarization tools that compute descriptive statistics for variables across all observations or within groups of observations. The SUMMARY procedure is very similar to the MEANS procedure; for full syntax details, see MEANS Procedure. Except for the differences that are discussed here, all the PROC MEANS information also applies to PROC SUMMARY." We covered PROC MEANS in the Programming 1 course. One of the main differences between MEANS and SUMMARY is where the output goes after it is created. MEANS generates a report table and SUMMARY generates an output dataset. That is the default behavior for each procedure, which you can always change. Cynthia ... View more

Hi: Programming 1 and Programming 2 are programming classes. If you have Enterprise Guide under a work or school license, then you can perform the work in the class using the Program Editor Window Enterprise Guide. There are explicit instructions in the Course Overview and Data Setup section of the course for how to make the class data using SAS Enterprise Guide. Most of the demos in class were recorded using SAS Studio to show the programming code. There are only a few demos that are specific to Enterprise Guide users in the Programming 1 class. The focus of the class is on writing code, which you can do in either Enterprise Guide or SAS Studio or other SAS environments.   If you do NOT have work or school access to SAS Enterprise Guide, then you do NOT need Enterprise Guide to practice the work in class. You can use SAS OnDemand for Academics and SAS Studio (in a browser) to use SAS on our cloud server to practice.   The training materials for the class are contained within the e-learning class itself. Have you activated Programming 1 yet? If so, look at the bottom of the Table of Contents page at the Resources section and you should see the Course Notes for class. However, also within the class itself, you will find the instructions to make the data, the instructions for each demo and the instructions for each practice are contained in the list of items for each Lesson. Cynthia ... View more

HI:   Have you thought about specifying the formula using TAGATTR? For example, in the code below, the EX1 workbook uses the data values for ACTUAL and PREDICT to calculate DIFF. But if I change any of those values in the worksheet after opening, the value for DIFF changes as soon as the value for either ACTUAL or PREDICT changes.   However, as shown in EX2, if I use computed items that are initially set to 0 (called C_ACT and C_PRED), then the columns are initially 0 when I open the output:     But as soon as I update the columns with values, the DIFF column changes: The code below shows both examples, but the screen shots are from the workbook created in EX2 code. ods excel file='c:\temp\formula_ex1.xlsx'; proc report data=sashelp.prdsale spanrows; where country eq 'CANADA' and year eq 1993; column country prodtype product actual predict diff; define country / group; define prodtype / group; define product / group; define predict / sum style(column)={tagattr='format:Currency'}; define actual / sum style(column)={tagattr='format:Currency'}; define diff / computed style(column)={width=1in tagattr='format:Currency formula:RC[-1]-RC[-2]'}; compute diff; diff=0; endcomp; run; ods excel close; ods excel file='c:\temp\formula_ex2.xlsx'; proc report data=sashelp.prdsale spanrows; where country eq 'CANADA' and year eq 1993; column country prodtype product c_act c_pred diff; define country / group; define prodtype / group; define product / group; define c_pred / computed style(column)={tagattr='format:Currency'}; define c_act / computed style(column)={tagattr='format:Currency'}; compute c_pred; c_pred = 0; endcomp; compute c_act; c_act = 0; endcomp; define diff / computed style(column)={width=1in tagattr='format:Currency formula:RC[-1]-RC[-2]'}; compute diff; diff=0; endcomp; run; ods excel close;   Using TAGATTR is an alternative approach. Cynthia ... View more

Hi: Most of the ODS output is proportional spaced font, so I"m not sure what you mean by "monocharacters". If you are going to change to a monospace font like Courier New, then number of spaces might work. The FLOW option is ignored for ODS destinations. What is your destination of interest. Did I miss whether you were using ODS RTF, ODS PDF, ODS HTML or ??? I see you mention RTF control strings, but I did not see ODS RTF statements in the code you posted. My tendency is to use INDENT= or LEFTMARGIN=, I think I've posted examples of both of those, but they depend on the destination. Cynthia ... View more

Hi: There were some special line breaking and line wrapping ESCAPECHAR commands in the original version of ODS ESCAPECHAR (V8.2). However, when ESCAPECHAR was revamped for SAS 9 I believe the special ones were deprecated and may not work in any destinations. Cynthia ... View more

You're right. Adding the %GLOBAL doesn't make a difference. However, the posted syntax was wrong, so that was my only purpose. Cynthia ... View more

Hi:   Well, there are a few issues that I see. The first one is that you should have %GLOBAL as the declaration statement and you need %LET to assign a value to the variable. As an example, this worked for me. I just used %PUT statements inside the macro program as proof that the values were being built correctly. I did not have any need to issue multiple LIBNAME statements: Hope this helps point you in the right direction. Cynthia ... View more

Hi: By default, when the system starts up, SASUSER.TEMPLAT and SASHELP.TMPLMST are set up by default. Theoretically, if you list SASHELP.TMPLMST first in the ODS PATH statement, that is the item store that is searched first. And if the production PROC FREQ template is found there, then that should stop the search there, even if SASUSER.TEMPLAT is in the list. My tendency is to NOT dump changed templates in SASUSER because every time you install SAS your SASUSER gets re-created, thus losing everything you saved there. Typically, I store templates in WORK while I'm testing and then send them to a permanent library that is not SASUSER (something like your PUB library). Putting the ODS PATH in your AUTOEXEC is a good way of dealing with the need to bump SASUSER.TEMPLAT out of the search path. You could try: ods path sashelp.tmplmst(read) sasuser.templat(update);     This approach works well for changed style templates that have different names than the production style templates. But the issue with the SASUSER that is the other reason I don't use it is that you don't want to give EVERYONE who will be using the changed template the code so they can each store the template in their SASUSER. Far better to put your production templates in your permanent library that's accessible to everyone and then the  the SAS production ones will be in  SASHELP and then for most people who will be sharing your templates, I'd recommend something like THIS in everybody's autoexec: ods path sashelp.tmplmst(read) myprod.templat(read); In other words, make the access level read for everyone except the programmers who will be allowed to change it. Cynthia ... View more

Hi:   Assuming you did NOT write into SASHELP.TMPLMST, then before you run your code, you should ONLY need to do this: ods path sashelp.tmplmst(read);   Do NOT put SASUSER.TEMPLAT into this path. What you're doing is removing the SASUSER item store from being searched when you use PROC FREQ. Assuming you only changed the template in SASUSER, then you should get the production PROC FREQ template with this statement in your code because you are telling ODS to ONLY search in SASHELP.     Let's keep our fingers crossed that you did NOT change SASHELP.TMPLMST, and when you use the ODS PATH statement, your PROC FREQ will be the default template. So then, when you want to use your changed template, you'd have to issue a new ODS PATH:  ods path sasuser.templat(update) sashelp.tmplmst(read); Which should then cause the changed FREQ template to be found first. What you're doing with the ODS PATH statement is changing what is available to be searched for  by ODS based on the templates used by the different procedures.   Now in the worst of cases, when you change the path to just SASHELP.TMPLMST and you do (unfortunately) still see the changed rejport, then you are sort of in Tech Support land. You should never, never, never, never, never, never, never, never, ever change SASHELP.TMPLMST to any access other than (READ). Depending on your platform, Tech Support may be able to just send you a copy of the item store for your version and maintenance level of SAS. In the ugly old days, if you accidentally wrote over a template in SASHELP.TMPLMST, you had to reinstall SAS to get the production templates back (guess how I know this). I don't think it's that way anymore, but I'm sending all good thoughts your way, that you only changed SASUSER.TEMPLAT.   Cynthia ... View more

Hi: Look in the Course Overview and Data Setup section at the top of the Table of Contents. There are 3 methods of making the data for your own SAS installation. The instructions you follow depend on the type of installation you have. If it turns out that you do not have SAS/Access for PC Files installed (this is what you need -- it contains the XLSX engine), then your best choice for practicing your be to use one of these options: 1) Use the Virtual Lab and SAS Studio that is INSIDE the course on the right side of the screen or 2) set up a SAS OnDemand account and use SAS Studio with SAS OnDemand to practice. There is NOT any data setup required to use option 1. There is 1 folder to make and 1 program to run to do the data setup for #2. Hope this helps, Cynthia ... View more

Hi:   Once the data are imported into 2 separate datasets, as you describe, this seems like a RENAME and a MERGE to start with. Something like this, given the 4 rows that you posted for each file (I called them FILE1 and FILE2): Of course, after being read in, using the same variable names in both files, if you want to merge them to get the final structure you described, then you've got to rename the variables as I show in the MERGE statement.   This is only getting you the structure you want. You'll have to write additional statements to do the validation and see whether there were changes in the values. The additional datasets created by using the IN= option in the MERGE, just show you how you can get the additional information about who was in one file without being in the other, who was in both files, etc. You could also have just made a "flag" variable instead of doing an output. I like to do the MERGE this way in order to validate the data and catch any really data problems. Cynthia ... View more

Hi: A single user account on the SAS OnDemand server has a limit of 5GB of disk space allocated to the Files (Home) folder. There used to be an upload limit on the size of files. I have not heard of an upload limit recently, if there is still one. I have heard of issues uploading with Safari. Better to upload files with Chrome or Firefox with SAS Studio. Cynthia ... View more