I use Access as my frontend and MySQL as back end.
I have a main table called client t1.
Clients have many Accounts t2 (1:M) between t1 and t2.
The accounts have Creditors t3 -technically a (Many Accounts :Many Creditors) relationship between t2 and t3.
Between the accounts and creditors there is currently no bridge table. I am using row source query to pull the t3 result and update it to t2. That is working fine albeit a bit slower than preferred.
According to 3NF and relationships - it is suggested that there should be a bridge table between t2 and t3.
My question is this in two parts:
A) If I create the bridge table (for normalization) what will that get me since it's already working (what is the biggest reason to do this here?)
What is the case to be made here for the junction or bridge table that is compelling in this scenario?
B) If I don't create the bridge table how will that hurt me ?
I have a main table called client t1.
Clients have many Accounts t2 (1:M) between t1 and t2.
The accounts have Creditors t3 -technically a (Many Accounts :Many Creditors) relationship between t2 and t3.
Between the accounts and creditors there is currently no bridge table. I am using row source query to pull the t3 result and update it to t2. That is working fine albeit a bit slower than preferred.
According to 3NF and relationships - it is suggested that there should be a bridge table between t2 and t3.
My question is this in two parts:
A) If I create the bridge table (for normalization) what will that get me since it's already working (what is the biggest reason to do this here?)
What is the case to be made here for the junction or bridge table that is compelling in this scenario?
B) If I don't create the bridge table how will that hurt me ?