Razzak:
I may have a simple structural misunderstanding.
[ ] One to Many (every slave is linked to the main)
[ ] Many to Many (every slave is linked to the main and also to other
slaves)
The first option I understand, no question
Example:
MainTable >> SlaveTable
Household >> StreetAddress
Household >> HomePhone
Household >> Person
But does the second option imply that every "lower" SubReport slave
table must contain a main-table column link even if these "lower"
SubReport slave tables link to the main only through "higher" SubReport
slave tables?
Example:
MainTable >> SlaveTable
Household >> Person >> MobileTelNum
Household >> Person >> EMailAddress
Household >> Person >> PersonalInfo
In this example, Person (say, husband | wife) link directly to
Household; but MobileTelnum, EmailAddress and PersonalInfo link directly
to Person, NOT directly to Household.
Would MobileTelNum, EMailAddress and PersonalInfo all need the linking
Household table column link as well? *1
Thanks so much,
Bruce
*1. Views or temp tables, no big deal.
------ Original Message ------
Sent: 2/23/2016 6:48:43 AM
Subject: [RBASE-L] - RE: Sub Report Question: Linking Column Names
From: "A. Razzak Memon" <[email protected]>
To: [email protected]
Cc:
At 09:25 AM 2/23/2016, Bruce Chitiea wrote:
Let me back up.
Main Report
Table0.EntityID
Sub Report_1
Table1.EntityID, Table1.PersEntityID
Sub Report_2 (Nested inside Sub Report_1)
Table2.PersEntityID
Sub Report_3 (Nested inside Sub Report_2)
Table3.PersEntityID
The values in question are missing from Sub Report_3.
Bruce,
Did you know that you can define a "Table Relations" when designing a
Report
with Sub-Report(s).
Here's how ...
While in R:BASE X Enterprise (Version 10) Report Designer ...
Main Menu > Tables > Table Relations ...
[ ] One to Many (every slave is linked to the main)
[ ] Many to Many (every slave is linked to the main and also to other
slaves)
In your specific scenario, use the appropriate option as you see fit.
That is your tip of the day!
Very Best R:egards,
Razzak
