Forum Discussion
MCFNeil
9 years agoQrew Captain
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.
JoshuaNorton
9 years agoQrew Member
I guess i'm a little confused on how that would work.
What I'm trying to do is create a report based off of one of the child tables, but have it display data linked from the other child table and the parent table.
Or have a parent table that can display data from both child tables.
So for example:
Lab table(child table), shows list of providers(child table) from a specific practice(parent table)
If the providers could be concatenated into one cell that would be perfect.
I'm wanting to see in the report:
Lab name | project name| provider(or list of providers concatenated in one cell)
...
...
What I'm trying to do is create a report based off of one of the child tables, but have it display data linked from the other child table and the parent table.
Or have a parent table that can display data from both child tables.
So for example:
Lab table(child table), shows list of providers(child table) from a specific practice(parent table)
If the providers could be concatenated into one cell that would be perfect.
I'm wanting to see in the report:
Lab name | project name| provider(or list of providers concatenated in one cell)
...
...