Liveware Publishing Support Forum

I cannot get what should be a simple multi scan report to work correctly. Here is the situation.____I use a database called DELAY. I group on two fields. The first is the Delay_Number and the second is the Delay_Date. For each Delay_Number there might be several Delay_Dates on file. For each Delay_Date there are labor charges that are tracked. In addition there is another database called MATERIAL which contains material costs associated with a particular Delay_Number. MATERIAL also contains a field called Delay_Number for the association. For each Delay_Number I want to report any Material costs as well as the labor cost already described. The report should look like this.__*********************************__Delay_Number one //Group 1__ Delay_Date one //Group 2__ labor costs__ labor costs__ Delay_Date two //another date__ labor costs__ labor costs__ ......__ labor costs__ Delay_Date // more date and labor costs for the first delay__ (Then want to display the material costs)__ Material Cost item one__ Material Cost item two__ etc for remaining material costs for this Delay_Number__ Then SUM all the Material costs.____Delay_Number two __ the report continues for all Delay_Numbers on file__***************************************__Id this possible with R&R version 8? I have an xBase++ application and are using dbf files and clipper ntx indexes____Thanks to all for the help in advance.____Jeff Stepek____

>I cannot get what should be __>a simple multi scan report __>to work correctly. Here __>is the situation. __>__>I use a database called DELAY. __> I group on two __>fields. The first is __>the Delay_Number and the second __>is the Delay_Date. For __>each Delay_Number there might be __>several Delay_Dates on file. For __>each Delay_Date there are labor __>charges that are tracked. In __>addition there is another database __>called MATERIAL which contains material __>costs associated with a particular __>Delay_Number. MATERIAL also contains __>a field called Delay_Number for __>the association. For each __>Delay_Number I want to report __>any Material costs as well __>as the labor cost already __>described. The report should __>look like this. __>********************************* __>Delay_Number one //Group 1 __> Delay_Date one __> //Group 2 __> __>labor costs __> __>labor costs __> Delay_Date __>two //another date __> __>labor costs __> __>labor costs __> __>...... __> __>labor costs __> Delay_Date // __> more date and __>labor costs for the first __>delay __> (Then want to display __>the material costs) __> Material Cost item __>one __> Material Cost item __>two __> etc for remaining __>material costs for this Delay_Number __>__> Then SUM all __>the Material costs. __>__>Delay_Number two __> the report continues __>for all Delay_Numbers on file __>__>*************************************** __>Id this possible with R&R version __>8? I have an __>xBase++ application and are using __>dbf files and clipper ntx __>indexes __>__>Thanks to all for the help __>in advance. __>__>Jeff Stepek __>__>____The problem you are seeing is your master file has many records for each delay_number as does your material file.__So each record from the master will find the same set of related records over and over.__One way to get around this would be to use a master file that has one record for each delay_number. You could even do a report and export the results to a DBF to create this file.__You could then from this master build scan relations to the DELAY and MATERIAL files and following the instructions in the multiple scan section of the R&R documentation get there.____The alternative is to work with what you have and use a logical record band for the material fields so that it would print only for the last date for each delay_number. To do that you would need two totals. One would be a count of dates reseting by delay_number, running and the second would be a count of dates reseting by delay_number, but Preprocessed.__The create a calculated field that says TOT1=TOT2 and use that as the condition for the MATERIAL record band.____Kathleen__R&R Support__

Thanks for the very quick reply. I think I understand what you are recommending and I will try it. I do need to pass along a little more information. The Material information is NOT related to the Delay_Date just the Delay_Number, so what I to show is just the Material info in a footer band(?) for the given Delay_Number. It does not seem to belong into a record band? ____Thanks again for a quick reply and a great product.____Jeff Stepek

It needs to go in a record band since you have multiple material records for each delay number.____Here is what the record structure looks like.__delay1 date1 material1__delay1 date1 material2__delay1 date2 material1__delay1 date2 material2____report will have a delay header, a date header and a logical record band with the material field so that output of above becomes____Delay1 __date1__date2__material1__material2____Kathleen__R&R Support