Sorry,

I'll give a better example tomorrow with data and without the m. vars.

Jake

On 12/18/07, Howard Schreier <hs AT dc-sug DOT org> <nospam@howles.com> wrote: > On Tue, 18 Dec 2007 22:22:40 -0500, Jake Bee <johbee@GMAIL.COM> wrote: > > >Howard, > > > >Thanks, I just found that use if ID in some literature just before your > >response, and the output is very nice, but it puts the output > >neatly on one page. I tried the use of a by statement, and the use of a > >view, but with the same results. So, I'm missing something. I included > >some example code with weeks and months (much shorter than the entire weeks > >/ year thing. > > Can't make much use of that without code to create table FINAL and create > the macro variables &N01_WEEK etc. > > > > >The only other thing that I can think of is to parse the final dataset into > >parts, and loop through the proc report with macro vars. > > > >Thought it would be easier if proc report had a was to control too many > >columns per page. > > > >proc report data=final split='~' spacing=1 center ls=132 ps=52 nowindows > >wrap headskip missing headline; > > column ('--' prim_sort > >termpref > > > > ('__No. % of Subjects > >Reporting__' > > > > ("__Rx Week 1__~&n01_week" > >stat_w25) > > > > ("__Rx Week 2__~&n02_week" > >stat_w50) > > > > ("__Rx Week 3__~&n03_week" > >stat_w75) > > > > ("__Rx Week 4__~&n04_week" > >stat_w99) > > > > ("__Month 1__ ~&n01_mont" > >stat_m01) > > > > ("__Month 2__ ~&n02_mont" > >stat_m02) > > > > ("__Month 3__ ~&n03_mont" > >stat_m03) > > > > ("__Month 4__ ~&n04_mont" > >stat_m04) > > > > ("__Month 5__ ~&n05_mont" > >stat_m05) > > > > ("__Month 6__ ~&n06_mont" > >stat_m06) > > > > ("__Month 7__ ~&n07_mont" > >stat_m07) > > > > ("__Month 8__ ~&n08_mont" > >stat_m08) > > > > ("__Month 9__ ~&n09_mont" > >stat_m09) > > > > ("__Month 10__ ~&n10_mont" > >stat_m10) > > > > ("__Month 11__ ~&n11_mont" > >stat_m11) > > > > ("__Month 12__ ~&n12_mont" > >stat_m12) > > > > ("__Month 13__ ~&n13_mont" > >stat_m13) > > > > > >)); > > > > > > > > define prim_sort / order=internal group > >NOPRINT; > > > > define termpref / order=internal group "Preferred Term" width=30 > >left flow; > > define stat_w25 / display "N (%) " width=15 > >center; > > define stat_w50 / display "N (%) " width=15 > >center; > > define stat_w75 / display "N (%) " width=15 > >center; > > define stat_w99 / display "N (%) " width=15 > >center; > > define stat_m01 / display "N (%) " width=15 > >center; > > define stat_m02 / display "N (%) " width=15 > >center; > > define stat_m03 / display "N (%) " width=15 > >center; > > define stat_m04 / display "N (%) " width=15 > >center; > > define stat_m05 / display "N (%) " width=15 > >center; > > define stat_m06 / display "N (%) " width=15 > >center; > > define stat_m07 / display "N (%) " width=15 > >center; > > define stat_m08 / display "N (%) " width=15 > >center; > > define stat_m09 / display "N (%) " width=15 > >center; > > define stat_m10 / display "N (%) " width=15 > >center; > > define stat_m11 / display "N (%) " width=15 > >center; > > define stat_m12 / display "N (%) " width=15 > >center; > > define stat_m13 / display "N (%) " width=15 > >center; > > > > > > break after prim_sort / > >skip; > > > > > > > > run; > > > > > > > >On 12/18/07, Howard Schreier <hs AT dc-sug DOT org> <nospam@howles.com> > >wrote: > >> > >> On Tue, 18 Dec 2007 21:24:36 -0500, Jake Bee <johbee@GMAIL.COM> wrote: > >> > >> >SAS-L: > >> > > >> >I have to produce output with proc report. The output is for AEs by Each > >> >Week in the Year. Naturally, there are more Weeks across than will fit > >> on > >> >one page. > >> > > >> >Is there a way to control this in proc report, such that each new page > >> will > >> >repeat the AE list, and continue the weeks where the weeks would > >> normally, > >> >without any control, > >> >continue to wrap on? > >> > > >> >Hope this is clear, if not I could provide an example, but I'm sure some > >> of > >> >you may have run into this situation. > >> > > >> >Thanks for any help, suggestions, literature! > >> > > >> >Jake > >> > >> I think you want the ID option in the DEFINE statement for the AE column. > >> >