You mentioned that status is a 10 character length field. Are you possibly wanting to delete a record if its status field contains an "A"? If so, you could use: data db.table; informat status $10.; length status $10; input status; cards; A BC A ABC BCD ; data temp_weekly_data; set DB.TABLE (where = (&date1 <= date_my < &date2 ) ); if find(status,"A") and datepart(date_my) < today() then delete; run; Art, CEO, AnalystFinder.com   ... View more

Assuming that your check will be against the observation count in a data set, here is a little macro that i use to return the number of observations in a data set. %macro obscnt(dsn); %local nobs dsnid rc; %let nobs=.; %* Open the data set of interest; %let dsnid = %sysfunc(open(&dsn)); %* If the open was successful get the; %* number of observations and CLOSE &dsn; %if &dsnid %then %do; %let nobs=%sysfunc(attrn(&dsnid,nlobs)); %let rc =%sysfunc(close(&dsnid)); %end; %else %do; %put WARNING: Unable to open &dsn; %put %sysfunc(sysmsg()); %end; %* Return the number of observations; &nobs %mend obscnt; in your program you might use it something like: %if %obscnt(mydata)>25 %then %do; ... View more

@Reeza excellent point  . ... View more

Thanks. it worked I actually had dups that I wasn't aware of.. ... View more

Hi, Please find below the code and its output:- ===================================== data new; informat mydate mmddyy10.; input mydate ; format mydate mmddyy10.; datalines; 03/01/2013 03/02/2013 03/03/2013 03/04/2013 03/05/2013 03/06/2013 03/07/2013 03/08/2013 03/09/2013 03/10/2013 03/11/2013 03/12/2013 03/13/2013 ; run; data new1(drop= month day year); set new; if weekday(mydate) NE 6 then delete; run; ===================================== Ouptut:- ============================================                                                          Obs        mydate                                                           1     03/01/2013                                                           2     03/08/2013 ============================================= /Daman ... View more

Hi:   You are asking for the MEAN statistic for your variable TARGET. That is the only statistic that PROC REPORT can give you at the break point on the report. If you want some other value, you will either have to 1) calculate it yourself and change the value within PROC REPORT 2) calculate it yourself outside of PROC REPORT and use a different variable for the summary inside of PROC REPORT 3) change the data before PROC REPORT, probably using FIRST. and/or LAST. logic to keep the first value for a group and then change to the SUM statistic. For example, if you changed your input data, temporarily, like this: NorthAmerica,Canada,100,1,10 NorthAmerica,Canada,0,2,120 NorthAmerica,Canada,0,3,75 NorthAmerica,USA,115,1,110 NorthAmerica,USA,0,2,20 NorthAmerica,USA,0,3,25 NorthAmerica,USA,0,4,15 NorthAmerica,USA,0,5,5 NorthAmerica,USA,0,6,5 NorthAmerica,USA,0,7,1 NorthAmerica,USA,0,8,7 NorthAmerica,USA,0,9,25 NorthAmerica,USA,0,10,65 Then the SUM statistic would work as you want when you do GROUPING and on the summary line for TARGET. If you remember, back in the first examples of this problem, you had two solutions -- one that used the MEAN (because your TARGET value was on every line) and one that used changed input data numbers and the SUM statistic. This is why you had those two different solutions -- due to the structure of your INPUT data and the way you represented TARGET in the input data. If you are getting a summary report (one row for every countryGroup/Country combination, then you do not need the TARGET number on every row. I don't quite understand the logic of why the values for NorthAmerica/USA changed from 100 to 10 to 5, while the values for CANADA stayed constant at 100 on each row. So there's probably more to understand about your data, but the bottom line is that PROC REPORT can only give you the statistic in the DEFINE statement automatically at a break. You can put another value in the cell using a COMPUTE block, but you have to know what the correct value is. cynthia ... View more

Hi:   The Days and Volume questions seems to have been asked and answered in this previous series of forum postings based on your earlier question: https://communities.sas.com/message/154885#154885   Like the other posting, it looks like the DAY variable is an ACROSS item (not a function). ACROSS is a DEFINE statement usage option. The country variable is going down the rows in the other report based on using GROUP as a DEFINE statement usage option. As I explained in the previous posting: 1) it would be more useful to see your data or a SAMPLE of your data 2) it would be useful to see the code that you have already tried 3) it would also be useful, when you show your code, to show your ODS destination. Why? Because, your destination of interest is immediately relevant to your wrapping question. Since you showed STYLE= overrides in the previous posting, it seems likely that you are using ODS RTF or PDF or HTML. ,An HTML page can be as wide as it needs to be, but RTF and PDF output is limited to physical page sizes. So, for your wrapping question, it seems likely that your destination is either RTF or PDF. This would be good information to have verified. You should not be experiencing wrapping in HTML tables. Options for dealing with wide tables with RTF and PDF destinations (I thought you only had 10 days) are to change the orientation to landscape, change the margin settings and/or change the font size, and cellpadding. All of these changes are outlined in an earlier post: https://communities.sas.com/message/414#414   When you ask whether there is an option that PROC REPORT can use to identify the "wrapped" columns, did you check the PROC REPORT documentation? The ID option on a DEFINE statement works as you describe. Here's the documentation link: Base SAS(R) 9.3 Procedures Guide, Second Edition cynthia ... View more