Thanks Paul
>>
>> How can create a report with mutiple detail bands. I have looked at
>> ReportX, but can't figure it out. Now I am using FoxFire, but can't find
>> the power / benefits. Which way to follow???
>
>FoxPro reports from a single table or cursor and, as such, can't report
>on multiple detail bands natively. But there are two ways around this:
>
>1) If you want multiple detail bands that immediately follow one
>another, for example an Invoice that lists a) line items; b) credits or
>discounts; and c) payments, then you can construct a cursor to manage
>this.
>
>Have an extra numeric field in the cursor that contains an ordinal for
>the type of line. "1" for Invoice Line Items, "2" for Credits, and "3"
>for payments, for example. Then have the 'separate' detail bands all
>drawn in the single detail band. For the labels and fields that are in
>the Invoice Line Items band, have the "Only Print When..." expression
>equal to: cursor.bandtype=1. Also ensure that you check the box that
>says not to print the line if blank.
>
>2) If you want three sets of detail bands printing in separate sections
>of a page, for example you want the invoice line items to take up most
>of the page, you want the credits in the bottom left corner, and you
>want the payments in the bottom right corner, then you can set up a
>cursor and two arrays.
>
>The cursor would contain the Invoice Line Items, the first array would
>contain the credit information, and the second array could contain the
>payment information. You can print a FoxPro memory variable on a
>report. And since an array element is simply a FoxPro memory variable,
>it's easy to print the arrays.
>
>Hope this helps
>
>/Paul
>
>--
>Paul Russell
>Software Kinetics Ltd. | Phone: (902) 481-4582 Fax: (902) 468-3679
>201 Brownlow Avenue | Office: Paul.Russell@SofKin.ca
>Dartmouth | "The best evidence that time travel will never
>be
>Nova Scotia, Canada | possible is that we have not been invaded by
>B3B 1W2 | hordes of tourists from the future." - S.
>Hawking
>
>"Use technology because it's appropriate -- except in the case of 'Java'
> then just use it 'cause it's cool!" - Paul Russell