Hi @heatherml20, a couple of notes:   1. There are extra 0's in the ELSE IF/THEN statement range for the Middle group. I recommend writing out large values with the comma separating every three digits (100,000) and then going through and removing the commas (100000) to ensure you're always capturing the right value.   2. The range for Sales has to be specified as a mathematical range in one condition ( a <= Sales <= b ) or as separate conditions combined with AND (Sales >= a AND Sales <= b).   3. No decimal places required here since we're capturing all values with integers.   Data shoerange; set sashelp.shoes; Length SalesRange $ 8; If Sales < 100000 then SalesRange = "Lower"; Else If 100000 <= Sales <=200000 then SalesRange = "Middle"; Else SalesRange = "Upper"; Keep Product Stores Sales SalesRange; run;     ... View more

Today marks a new beginning, we’re starting our SAS Programming 2: Data Manipulation Techniques course! I hope you’ve had a chance to go through the following on your own time before class:  PG1: Lesson 6 & 7 | all | practices, activities  PG2: Lesson 1 - 2.1 | e-learning  See you all in class this afternoon!  ... View more

This might just be a feature of the data. Where is this filtering taking place or what is it that you're trying to achieve? ... View more

The data would need to be pre-processed before you use it in Visual Analytics for reporting. This can be done with SAS Studio, using SAS code or tasks.  ... View more

@NewUsrStat, I should also mention that running your DATA step to create DB didn't work. By default, when you reach the end of the line and there are missing values for the remainder of the variables, SAS will continue reading from the next line. Hence the message below: "SAS went to a new line when INPUT statement reached past the end of the line".      You'll want to add in the option TRUNCOVER like so:   data DB; infile cards truncover; input ID :$20. Admission :date09. Discharge :date09. Sex $; format Admission date9. Discharge date9.; cards; 0001 13JAN2017 25JAN2017 M 0001 22FEB2018 03MAR2018 0001 22FEB2018 03MAR2018 0002 01DEC2016 14DEC2016 F 0002 01DEC2016 14DEC2016 0002 25DEC2017 02JAN2018 0002 06JAN2018 09JAN2018 ; run;   ... View more

Hi @trytolearnsas, you can filter the values from the  Filters pane on the right (second last icon):   In this case, you'll want to uncheck the box at the bottom for "Include missing values".   ... View more

Thank you everyone for your participation in class last week. Today, we’re doing it all again! Week 6 will focus on Exporting Results and Using SQL, so please make sure you’ve completed the following from the Programming 1: Essentials course:  Lesson 5 | all | practices, activities  Lesson 6 & 7 | all | e-learning  Happy reviewing, we’ll see you soon!  ... View more

Good afternoon everyone, and welcome back for another week of SAS Programming! Today’s session will focus on the analysis and reporting of data. Review the following materials from Programming 1: Essentials in preparation:  Lesson 4 | all | practices, activities  Lesson 5 | all | e-learning   Bring all your questions to class or post them here. See you all very soon!  ... View more

Hi @pallaviarora26, I have sent you the link to the recordings in a private message. The recordings will be available for 20 business days from our last session.  ... View more

No worries! That's what we're here for. Hopefully this helps others too 😊 ... View more

Hi @OliviaOk, you're on the right track! When you submit a %LET statement to create a macro variable, you will not see any messages in the LOG. That macro variable is "quietly" created and it is storing the value you specified.     The issue I see with your code is that you are seeing an ERROR message right after the PROC EXPORT DATA= statement. It hasn't even reached the part where you are using your macro variable. The reason for this is that you have too many semicolons (being interpreted as the end of statements).  Notice in the syntax example above your code that the PROC EXPORT statement ends with one semicolon after the REPLACE option, 3 lines later.    TLDR: there's nothing wrong with the macro variable definition or use, the ERROR comes from having extra semicolons in your code and I've highlighted them below.          ... View more

We’re nearing the end of our series and by now you’ve discovered insights in your data and are ready to show them off. Rachel will teach us today how to create beautiful, interactive reports in Visual Analytics so your patterns jump off the screen! See you all shortly for our last session together.  ... View more