The error message is telling you that RESRISK is not a valid option in your version of Surveyfreq. Since the documentation for the procedure at https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/statug/statug_surveyfreq_syntax06.htm does not include RESRISK where did you get that as an option? With that error no output should be generated.   So make sure you use RELRISK, not RESRISK.   If you want ODDS Ratios for more levels you may be looking at Proc Surveylogistic. ... View more

From this code LABEL is not valid within the SERIES statement.   proc sgplot data=freqout2 ; where ever_told_mi=1; series x=year y=pct_row / markers lineattrs=(thickness=2px) group=cann_use_status DATALABEL=pct_row; ; series x=year y=AVG_VALUE / markers lineattrs=(thickness=2px) y2axis DATALABEL=AVG_VALUE; *values=(2009-2010 to 2017-2018); yaxis label = "Percentage Reporting Prior MI" values=(0 to 100 by 10) VALUESFORMAT=f8.1; y2axis label = "Percentage Reporting Current Use" values=(0 to 100 by 10) VALUESFORMAT=f8.1; format ever_told_mi yes_nofmt. cann_use_status cann_use_statusfmt. pct_row 8.1; run; ... View more

@SAS_Rob Thanks for the response.  2 clarifying questions: <place the domain variable itself on the TABLES statement> 1. Could you please clarify?  For example, using PROC SURVEYLOGISTIC I would add the following (see below): domain flag_2; proc surveylogistic data=&dataset nomcar; stratum sdmvstra; cluster sdmvpsu; weight &weight; /* DOMAIN: used instead of the WHERE or BY statement to provide analyses of subgroups. */ domain flag_2; class &exp (REF="Never")/param=ref; model ever_told_mi (descending) = &exp; format ever_told_mi yes_no_fmt. &exp cann_use_statusfmt.; run; Are you saying that for PROC SURVEYFREQ you just include the variable w/o the DOMAIN statement, like this?  proc surveyfreq data=&dataset nomcar; STRATUM sdmvstra; CLUSTER sdmvpsu; WEIGHT &weight; table flag_2*&exp /cl col chisq; format &exp cann_use_statusfmt.; run; 2. Are you saying that the DOMAIN statement IS available with the SURVEYFREQ procedure, or are you just saying you can mimic its functionality w/o specifying the actual statement by adding the DOMAIN variable to the TABLES statement?  Thanks! ... View more

Sorry for not being more clear...The VALUESFORMAT= option formats the decimal places on the axis, which I also wanted. I was wanting to format the values of the Y variable and your response jogged my memory. I just need to format the Y variable. Duh. Thanks!  ... View more

Assuming that the desired complete sets always occur in the sequence     baseline_arm_1     fu_1_arm_1     fu_1_arm_2 you can do a "lookahead" merge to determine whether the current record and the two subsequent records should be output (untested)::   data want (drop=_:); merge have have (firstobs=2 keep=redcap_event_name rename=(redcap_event_name=_nxt_evnt)) have (firstobs=3 keep=participant redcap_event_name rename=(participant=_nxt_part2 redcap_event_name=_nxt_evnt2)); retain _counter 0; if _counter<=0 then do; /*If not already in a threesome, then check the lookaheads */ if redcap_event_name='baseline_arm_1' and _nxt_evnt='fu_1_arm_1' and _nxt_evnt2='fu_2_arm_2' and _nxtpart2=participant then _counter=3; end; if _counter>0; _counter+(-1); run;   Editted note:  slightly cleaner code below:   data want (drop=_:); merge have have (firstobs=2 keep=redcap_event_name rename=(redcap_event_name=_nxt_evnt)) have (firstobs=3 keep=participant redcap_event_name rename=(participant=_nxt_part2 redcap_event_name=_nxt_evnt2)); retain _counter 0; if redcap_event_name='baseline_arm_1' then do; /*If this is baseline, check the lookaheads */ if _nxt_evnt='fu_1_arm_1' and _nxt_evnt2='fu_2_arm_2' and _nxtpart2=participant then _counter=3; end; if _counter>0; _counter+(-1); run; ... View more

It is not hard to run a little test to see what it does. 1733 data _null_; 1734 do yrs=1,5,7,10,12 ; 1735 put yrs= yrs yrs.; 1736 end; 1737 run; yrs=1 < 5 yrs yrs=5 5-10 yrs yrs=7 5-10 yrs yrs=10 5-10 yrs yrs=12 > 10 yrs If you want to exclude one of the boundaries from a range place a < on that side of the hyphen. proc format; VALUE yrs low-<5 = "< 5 yrs" 5-<10 = "5-10 yrs" 10-high = "10+ yrs" ; run; Result 1745 data _null_; 1746 do yrs=1,5,7,10,12 ; 1747 put yrs= yrs yrs.; 1748 end; 1749 run; yrs=1 < 5 yrs yrs=5 5-10 yrs yrs=7 5-10 yrs yrs=10 10+ yrs yrs=12 10+ yrs ... View more

Hello @_maldini_  It is good that your issue is resolved. The screen capture of the error message you have posted, indicates that network has discoonected/no network connection.   ... View more