Child report table on Parent record
So I need an answer to 2 questions here: 1) How do I get the child report table that appears on the parent record to extend all the way accross the screen. I have attached a pic. 2) Is th...
Forum Discussion
Joshua,
Rather than making a reverse relationship, I'd recommend making a joined table.
Call it something like "Practice Providers".
Each Practice will have many practice providers
AND
Each Provider will have many Practice Providers.
Then you can have multiple assignments and gives you a lot more flexibility for reporting, and appointment setting.
Rather than making a reverse relationship, I'd recommend making a joined table.
Call it something like "Practice Providers".
Each Practice will have many practice providers
AND
Each Provider will have many Practice Providers.
Then you can have multiple assignments and gives you a lot more flexibility for reporting, and appointment setting.
re: "Or have a parent table that can display data from both child tables."
You can float up data form a limited number of children. I had asked how many, in practical terms you will have. Let's say that in practical terms, 5 is enough.
The technique is edit the relationship between 1 parent has many Children to make a summary of the Minimum Record ID# of the child records. Call it [Minimum Record ID of Providers #1]. Look that field up down to the Child table.
Then make a reverse relationship where 1 child has many parents and on the right side use the field [Minimum Record ID of Providers #1]
Lookup the text value to the parent Practice record.
Then duplicate the field [Minimum Record ID of Providers #1] and call it [Minimum Record ID of Providers #2]
But change the Summary filter to make it the minimum record id# subject to the condition that the [Record ID#] > [Minimum Record ID of Providers #1]. On the main "forward" relationship, lookup that [Minimum Record ID of Providers #2] to the child table.
Conveniently, QuickBase will have duplicated the reverse relationship when you duplicated that field. Edit that relationship to look up the text value to the Parent record. That's two so far we have done.
Basically just keep going and looping. if you have say a half a dozen to do, then it will work OK., if you have dozens of loops to do, then you risk getting into performance issues with your app.
Once you get enough of them floated up, you can concatenate them together with a List function)
You can float up data form a limited number of children. I had asked how many, in practical terms you will have. Let's say that in practical terms, 5 is enough.
The technique is edit the relationship between 1 parent has many Children to make a summary of the Minimum Record ID# of the child records. Call it [Minimum Record ID of Providers #1]. Look that field up down to the Child table.
Then make a reverse relationship where 1 child has many parents and on the right side use the field [Minimum Record ID of Providers #1]
Lookup the text value to the parent Practice record.
Then duplicate the field [Minimum Record ID of Providers #1] and call it [Minimum Record ID of Providers #2]
But change the Summary filter to make it the minimum record id# subject to the condition that the [Record ID#] > [Minimum Record ID of Providers #1]. On the main "forward" relationship, lookup that [Minimum Record ID of Providers #2] to the child table.
Conveniently, QuickBase will have duplicated the reverse relationship when you duplicated that field. Edit that relationship to look up the text value to the Parent record. That's two so far we have done.
Basically just keep going and looping. if you have say a half a dozen to do, then it will work OK., if you have dozens of loops to do, then you risk getting into performance issues with your app.
Once you get enough of them floated up, you can concatenate them together with a List function)