Maybe I'll wait for v7 - I recall some of the EARLY work w/multi-column
("snaking") reports/labels fm ca. 1987 - man, that was cool thinking - but I
don't think it's worth it f/what is now more of an "ad hoc" solution.Thanks, Steve in Memphis ----- Original Message ----- From: "David M. Blocker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 30, 2002 12:55 PM Subject: Re: REPORTS. Keep Next/Previous Section Together > Steve > > These marks on the report screen do not mean what you think - it means keep > the HEADER ITSELF together: if there is not enough room for the HEADER lines > on the current page, go to the next page. > > What you want is to tell R:Base: "if there is not enough room for the ENTIRE > BREAK SECTION: header / detail / footer on this page, don't print - start on > the next page. > > Under 6.5++, you have four choices: > > 1. Create a form feed for each break - each new group starts on a new > page - easy to do on the Breakpoints screen > 2. Live with it as is > 3. With a minor change, you can repeat the break header on the next page > with the words "continued". If interested in details, ask and I'll provide. > 4. With a LOT of trouble, you CAN create a complex set of variables on the > report and calling program to do what you want to do. I can send a sample > if you want. > > OR, wait for 7.0 where it will be easy!! > > David Blocker > > ----- Original Message ----- > From: "J. Stephen Wills" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Monday, September 30, 2002 11:10 AM > Subject: REPORTS. Keep Next/Previous Section Together > > > > This ought to be basic, but my understanding is insufficient. It seems > that > > no matter how I check these checkboxes in > REPORTS:LAYOUT|CREATE_BREAKPOINT, > > Pg-Brk's occur in the middle of a section. > > > > I have defined in my Report : > > > > PH > > H1 > > H2 > > D > > F1 > > PF > > > > The Pg-Brk's seem to occur in the middle of the Detail section. Does > > checking these boxes only apply to Break-Headers/Footers? If so, should I > > "convert" my Detail lines to Break-Footers? I don't know if that's always > > possible, but it should be w/this particular report. > > > > Would somebody be so kind as to assist me in understanding these and maybe > > fm there I could move fwd w/this? > > > > Thanks, > > Steve in Memphis > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > > TO SEARCH ARCHIVES: > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
