Many to many table realtionship

  • Thread starter Thread starter Frank Situmorang
  • Start date Start date
F

Frank Situmorang

Hello,

I have read some explanantions about many to many table relationship, but it
is not so clear to me in practice.

My church membership database that I am going to make will include list of
church officers or servents we can say.

I have table members, addresses and servents. I am working on member and
address which have one to many and seems no problem, but now between servents
and members, it will be many to many and I do not quite undestand the
explanation we have to make one connection table in order to have many to many

Is there any sample of database that we can download? maybe by that I will
understand it.

in our Seventhday Adventis churches in Indonesia , One servent/officer
position could have many members, but also a member could have 2 ( many)
postions like church elder and church committee member etc.

If anyone could help me so that I can finish my project. I want to give my
project for the church freely.

Sorry I am not too good in access because my specialty in fact is
Accounting, but by selfthought it seems I can progress in learning this
accessdatabase
 
Sounds like you have several roles (position/officerships) people hold, and
one person can hold several positions.

So you need a table that lists the possible roles. Fields:
RoleID primary key
RoleName text

You already have a member table (one record for each person), fields:
MemberID primary key
Surname family name
FirstName Christian name

The 3rd table will have fields like this:
MemberRoleID autonumber primary key
MemberID relates to Member.MemberID
RoleID relates to Role.RoleID
RoleStart Date/Time when this person started in this role.
RoleEnd Date/Time when this person ceased in this role.

You will interface this with a main form bound to the Member table, and a
subform count to the MemberRole table. The subform will be on Continuous
Form view, so if a person has multiple roles you can then them in the
subform (one per row.) Use a combo box for the RoleID in the subform.

HTH
 
Back
Top