My question is.... Can you break on a variable? I have a report that does not seem to be breaking on reports. In other words, if an order has two or more items of the same thing, the invoice breaks on the description, but it is not putting them together.
Thanks Kristie -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Marc Sent: Thursday, June 19, 2008 3:44 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Printing reports break points Order by Hi There are 3 kinds of Breaks on the Report Data Custom Var I just finished making 5 Data Breaks and the report prints the same as my old 3 breaks and Order by clause. But when I click on the Custon and Var breaks there are now 5 breaks and one of them is different than the 5 data breaks I set. So, what do those do or should I be concerned about those? thanks Marc ----- Original Message ----- From: "Lawrence Lustig" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Thursday, June 19, 2008 1:36 PM Subject: [RBASE-L] - Re: Printing reports break points Order by > << > So do you need an Order by clause ? Does it > help? >>> > > No, it hurts. If you have breakpoints, don't use an ORDER BY clause. > > << > If you want to have the same report but Order it by > custnum or Lastname ... do you > have to have 2 different > reports? >>> > > You can deal with this in a number of ways: > > 1. Have a report with no breakpoints -- you are free to use an ORDER BY > clause to determine how this prints. > > 2. Manipulate the data so that the same report takes on a different > appearance when printed. For instance, add columns SORT1, SORT2, and > SORT3 to your table and set your breakpoints on these columns. Before you > print, update SORT1 with the customer number if sorting by number, or the > customer name if sorting by name. Better yet, base the report on a > temporary view with extra columns to handle the sorting and recreate the > view immediately before printing with the user-specified columns in the > extra columns used to specify sort order. > > This works best if you don't have data placed in your break headers and > footers (since that data layout would likely be different for different > sort orders). But even there, if you're willing to limit what appears in > those report sections you can use the method described above and simply > add extra columns like BREAKNAME1 and so on to store the data. > > There are a few situations in which you may really want to combine report > breaks and ORDER BY -- for instance, if the _first_ breakpoint is always > the same (eg State), and is heavily formatted while the following > breakpoint changes and has no header or footer (eg Customer Number vs > Customer Name). In this case you can use the report break and then an > ORDER BY to control the second level sorting, but they must have the same > number of entries. > -- > Larry > > --- RBASE-L ================================================ TO POST A MESSAGE TO ALL MEMBERS: Send a plain text email to [email protected] (Don't use any of these words as your Subject: INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: INTRO ================================================ TO UNSUBSCRIBE: Send a plain text email to [email protected] In the message SUBJECT, put just one word: UNSUBSCRIBE ================================================ TO SEARCH ARCHIVES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: SEARCH-n (where n is the number of days). In the message body, place any text to search for. ================================================
