You won't be able to cascade deletes or enforce referential integrity though.
Main Topics
Browse All TopicsWe've got 4 primary tables: Branches, Employees, lenders, and loans.
There's a many to many relationship between branches and employees,
and a many to many relationship between branches and lenders. (branches have to be approved with lenders)
So we need a way to relate Branches, employees, and lenders to loans without creating a circular relationship.
Any ideas?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
To create a many to many relationship you have to create an intermediate "linking" table. This table holds the primary keys of the two other tables. Since you have two many to many relations you need two of these tables:
tblEmployees tblEmpBranch tblBranches tblBranchLender tblLenders tblLoans
Emp_ID------------<Emp_ID Lender_ID>----------Lender
Branch_ID>----------------
Fred, thanks for the correction that was what I meant.
So with loan_id added to the tblEmpBranch
tblEmployees tblEmpBranch tblBranches tblBranchLender tblLenders tblLenderLoan tblLoans
Emp_ID-----------<Emp_ID Lender_ID>--------Lender_I
Branch_ID>---------Branch_
Loan_ID>------------------
There is a one to many relationship between loans and lenders, a loan could be assigned to multiple lenders. Like my mortgage ;)
But if that is not a requirement and a loan can only have one employee, branch and lender you should add this information as foreign keys to the loans table.
tblLoans
loan_ID
lender_ID
emp_ID
branch_ID
remove the loan_ID from the tblLenderLoan
Can one employee be associated with multiple branches? If so, then you need to have
tblBranch tblEmployessAtBranch tblEmployees
BranchID<----------->Branc
EmployeeID<-------------->
tblLenders tblLendersAtBranch tblBranch
LenderID<---->LenderID
BranchID<---------------->
tblLenders tblLendersPerLoan tblLoans
LenderID<----->LenderID
LoanID<----------------->L
You need to either store the BranchID and Employee ID in the loan table, or make up a seperate table that has
tblLoanLinks
EmployeeID
BranchID
LoanID
Then you could take any one piece of information and solve for the other 3, so you can see all the loans made by an employee at any branch or any lender, or all the lenders for a branch regardless of the employee.
Business Accounts
Answer for Membership
by: thebiggillsterPosted on 2003-06-10 at 13:31:01ID: 8694256
Use a saved query and make the joins in the QBE window. Access treats saved queries exactly the same as a table