Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Does VFP9 Reports support grandchild tables?
Message
From
20/12/2006 16:28:43
 
 
To
20/12/2006 15:14:28
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Miscellaneous
Thread ID:
01179329
Message ID:
01179355
Views:
8
Hi Craig,

I am going to guess that you mean to "denormalize" the child - grandchild table so that the "header" info from the child table is repeated for each grandchild record - and then I supress repeated values of the child info so that the child info only prints once?

Albert

>Grandchildren are not directly supported in detail bands. However, you can trick the report designer by doing SQL JOINS of tables and using multiple detail band objects controled with PrintWhen conditions.
>
>
>>Hi Everyone,
>>
>>You can just respond to the question in the thread title. For a bit of an explanation (that might prompt a workaround), here is what the client wants.
>>
>>Law firm...wants to print detail of a single client file. Here are the tables and their relationships:
>>
>>MainTable: Plaintiff, heading detail (name, date of birth etc; used to print in header area)
>>
>>--> ChildTable1: contacts on this file (multiple, related to main by File_ID)
>>
>>--> ChildTable2: annuities purchased for plaintiff; multiple; related to MainTable by File_ID
>>
>>-----> GrandChildTable1: who purchased each annuity (multiple litigants may have contributed to purchasing the annuity); related to ChildTable2 by Annuity_ID
>>
>>Results so far: I can get the info to print but the GrandChildren print *after* all of the ChildTable2 records whereas I would like the info to "interleave" in between each annuity e.g. (showing just the annuities):
>>
>>Annuity 1: Sun Life of Canada, Total Premium: $10,000.00
>> ---> Crash Dummies Casualty Co, Contributed: $5,000.00
>> ---> Total Wrecks Insurance Co., Contributed: $5,000.00
>>
>>Annuity2: The Manufacturers Insurance Co., Total Premium: xxx.xx
>>etc.
>>
>>It could be that I am not putting in the right "target alias" for that expression (I have tried several). I am currently putting in "GrandChildTable1".
>>
>>Thanks for any help.
>>
>>Albert Gostick
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform