Hi: If the student is reporting a problem with one of our SAS Education e-learning classes, then they can report the problem to elearn@sas.com and the instructors on duty will investigate and help. Cynthia ... View more

Hi:   SAS OnDemand for Academics does not have a SQL server -- either MySQL or MS-SQL server available. PROC SQL is primarily intended for students and independent learners to learn how to use the SQL procedure, at the level that we teach in the Programming 1 and SQL 1 classes. We do NOT use any external databases in these classes. Cynthia ... View more

Hi: You will not be able to install a mysql server into the SAS ODA file system. The SAS OnDemand server does not provide users with that kind of access to the operating system. And, as you have discovered, the SAS OnDemand for Academics server can only work with uploaded files, it cannot read from your local machine to access your database. Cynthia ... View more

Hi:   You might also want to search in the documentation and on the support web site. For example, in this example contained in this Tech Support note: https://support.sas.com/kb/25/401.html   You can see that the color for each column inherits the color of the header under which the column is nested. This is known as using style=<parent> which is a style override feature of PROC TABULATE. This feature allows you to do either horizontal or vertical "banding" based on the style characteristics that you associate usually with a CLASSLEV header variable. Cynthia   ... View more

Hi: If you have a SAS Profile with your .EDU email address and you have activated the SAS Skill Builder Portal, these type of Macro topics are covered in the SAS Macro Language classes that are available to you inside the Skill Builder Portal. Cynthia ... View more

Also, keep in mind that SAS OnDemand for Academics has the ability to automatically create PDF and RTF files, so you will want to turn OFF the automatic file creation. Also, you'll need to find the RTF file created in your OnDemand folder and download it from the OnDemand server to your local machine so you can open the file with Word. Cynthia ... View more

Hi: If the code you've posted works with your data, then somehow in the process of writing your macro program(s), the code you're generating is not correct syntax-wise or not correct within the context of PROC REPORT. Cynthia ... View more

Much of PROC REPORT processing depends on seeing ALL your code. We need to see the order of variables in your COLUMN statement and the usages in your DEFINE statements. Without this type of context, it is hard to comment constructively on your question. You indicated that your code works when it is not macro-ized. However, something is "breaking" when your code is macro-ized. I am particularly confused by the word "BREAK" that appears in your question. There is not a statement in PROC REPORT that is the single WORD "BREAK" without a BEFORE or AFTER and a variable name or a location. In addition BREAK processing in PROC REPORT occurs at explicit places, and it would be hard to force a BREAK between COMPUTE blocks as you seem to imply. But, as I said, without seeing the code that works and ALL of your macro code, it is hard to comment. And, of course, without data, nobody can test or tweak your code. Cynthia ... View more

Hi: If your CHOL variable is numeric, then you are referencing the variable incorrectly in your COMPUTE block. Remember that the default usage for a numeric variable is ANALYSIS with a default statistic of SUM. Inside a COMPUTE block when you are using a numeric variable in code, you need to use the compound name: variable.statistic so that PROC REPORT knows which value to use in the comparison. In this case, I would expect that CHOL.SUM might work instead of just referring to CHOL in your IF statement. Also, I wonder at your GROUP usage for GENDER and AGEGROUP and whether they might be impacting your values for CHOL and WBC because the default behavior of GROUP would cause your values for CHOL and WBC to be summarized. In addition, you have WBC listed twice, once with a usage of ANALYSIS/SUM and last with a usage of DISPLAY. So it seems like there are some possible issues to clean up in your code. Also, specifying WIDTH=8 is a setting that is ignored for ODS destinations. I'm also curious about the usage for SUBJECT, if it is Character, the default usage would be DISPLAY, but it appears to be NUMERIC, in which case, I'm not sure what purpose SUBJECT is serving on this report. Are there any WARNINGS or ERRORS in your SAS Log? Cynthia ... View more

Hi, I'm not sure why you need a macro program or macro definition to do this. You can easily do what you want with array processing. And I'm not sure I understand what you mean when you say that you want a "macro" that contains all variables. Do you mean you want one Macro variable that contains ALL the rows you listed as one macro variable value? Or do you mean you want one macro variable for each year so that a reference like Varlist_&tb._&yr would return the varname value that you want? Cynthia ... View more

Hi: This is a behind the scenes (internal to EG) process that is not under your control. In the end, the issue with transcoding is going to be with the data and the encoding settings on the data, system, server, SAS session, etc. Rather than trying to reverse engineer how EG does it, try some other approaches that may help you determine the actual root cause. For example, when you use the XLSX engine or PROC IMPORT, do you have the same transcoding errors? Have you examined the data to see what the original encoding for the data file or the XLSX file was? Have you tried checking the ENCODING= option as a system option and within your code. If you can't get to the bottom of the transcoding problems on your own, then it's time to open a case with SAS Tech Support for more directed help in debugging and solving the issue. Cynthia ... View more

Hi: Just a thought. Macro variable references cannot be resolved in single quotes. So every place that you reference 'gaint_&var..sum' you will need to change the code to "&gaint_&var..sum" or otherwise, PROC REPORT will not be able to get a valid variable name at resolution time. Cynthia ... View more

Hi: In addition, you do NOT show your entire COLUMN statement. Do you use any ACROSS variables? Are any of your ANALYSIS or COMPUTED items under an ACROSS variable? The only scenario that will work with the statements as you show them is if there are NOT any ACROSS variables used with these ANALYSIS or COMPUTED items. Cynthia ... View more

Hi: To add to @ballardw excellent response, my advice is to NOT try to MOVE within the existing document store. I prefer to keep a "good" original document store unchanged, as created by the procedures, and than start fresh in a new document store to build the structure I want and then copy the objects from the original document store to the restructured document store. Let me say that this is just my preference. However, it is the reason why I cannot offer any other advice because I just don't use MOVE. However, having the original document store to fall back to when I mess up has been very useful. My approach for a need to restructure would be to build my new document store, make the folder structure and then copy each item into the new folder structure. I do remember being able to replay using WHERE, but I do not recall being able to use the WHERE in a COPY (or MOVE) statement in PROC DOCUMENT. Did you check the documentation and paper examples for ODS DOCUMENT and PROC DOCUMENT?? Cynthia ... View more