>>>>>>I've created a report with a child and a parent that
>>>>>>has a relation and a skip set prior to the run of the
>>>>>>report. The totals located in the group footer section
>>>>>>is sometimes forced to the next page because of the number of child records on the first page. Unfortunately the information in the group header on this 2nd page is
>>>>>>incorrect showing the following records information. I
>>>>>>have many different solutions, including tying a custom
>>>>>>object to the report that will display this group header information. Nothing seems to be working.
>>>>>>
>>>>>>
>>>>>>Thanks in advance.
>>>>>>
>>>>>What fields are using for relation, report grouping and what fields should be displayed in Group Header Band?
>>>>
>>>>
>>>>Do you want to meet at the VFP conference room. That might be a
>>>>little faster.
>>>>
>>>>Dan
>>>
>>>Sorry, it doesn't work on my machine. Moreover, I feel my users want to catch me . But you can post your reply and I will be back during the day.
>>
>>Ok. The Parent table holds Dealer Information such as
>>Dealer Name, Dealer Number and balances. I link to the
>>child with Dealer Number. Originally I tried using set
>>relation to and set skip to. But this didn't work because
>>I needed to see each parent whether it had any child
>>transactions or not. Somebody suggested an SQL select
>>with an outer join. I was able to get the desired result
>>using set fields and just copying the information to a
>>3rd file which I use in the report.
>>
>>
>>In the group header. I place the Dealer name info.
>>
>>In the Detail band I list all the transactions.
>>
>>In the group footer. I list all the balances.
>>
>>eg.
>>
>>******
>>* Page 1
>>* Footer
>>Dealer No. - 214 Dealer Name - Deals On Wheels etc.
>>
>>* Detail
>>35 lines of details
>>* footer information is forced to the next page
>>
>>
>>*Page 2
>>*Group Header
>>*Dealer No. - 215 Dealer Name - Corrubian Auto Sales etc.
>>
>>*Detail band
>>*No Details
>>
>>*Group footer
>>*Actually displays balances of the prior dealer 214.
>>
>>Dan
>
>I don't know who suggested outer join, but this is right solution, because the problem originated from parent record w/out child (no detailes). Basically, I don't like temp relationships because they involve problems behind-the-scene, and this is one of them.

Ok. I tried the outer-join solution but unfortunately the group
header is still showing the following records info.

Dan