Results 1 to 4 of 4
  1. #1
    Join Date
    Aug 2015
    Posts
    2

    Unanswered: Membership database setup

    Good afternoon,

    I am trying to setup a membership database in Access 2010 for our club.
    The hardest part is to setup the ER database right.
    I already made an initial setup, but during this setup I noticed some more difficulties.

    Click image for larger version. 

Name:	database.png 
Views:	5 
Size:	44.6 KB 
ID:	16514

    In our club we have four kind of members:
    - Full member
    - Family member
    - trial member

    The full members know two types: normal and breeder
    You can only become a trial member by a breeder.
    So the breeder informs the club which new trial members there are to added.

    And then we have a family member.
    Someone can only take the family membership if someone else has a full membership on the same address.

    So in the included image you can see I already made de trial member table (tblPuppyProefLeden) which has a relation with the breeders (tblFokkers).
    You can also see the full members (tblVolwaardigeLeden) and the family members (tblGezinsleden)

    I also made a table contactpersons (tblContactPersonen) which contains the names addresses etc for the trial, breeders, family and full members.

    My problem is now that breeders are also full members, so how can I relate them.
    And as you can so seein the tables tblFokker, tblVolwaardigeLeden and tblGezinsleden I used "automatische incasso" and "Opgezegd per".
    Should I normalise this?

    And my last question / problem how can I connect all the member tables (tblPuppyProefLeden, tblFokker, tblVolwaardigeLeden and tblGezinsLeden) in the right way with the table tblContactpersonen.

    I hope I made my self a little bit clear what my challenges are.

    with kind regards,

    Hammie

  2. #2
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    496
    Provided Answers: 24
    I dont see the need for various member tables. There should be 1, tPersons.
    A person will have a field [MemType] with values:
    Full
    family
    trial

    then you can send mail to all full members , or only trials, etc.

    Note, I made a separate table for addresses tAddr because several members live at the same address.
    tPerson.AddrID is the key to that table.

  3. #3
    Join Date
    Aug 2015
    Posts
    2

    Thank you

    Quote Originally Posted by ranman256 View Post
    I dont see the need for various member tables. There should be 1, tPersons.
    A person will have a field [MemType] with values:
    Full
    family
    trial

    then you can send mail to all full members , or only trials, etc.

    Note, I made a separate table for addresses tAddr because several members live at the same address.
    tPerson.AddrID is the key to that table.
    Thank you for your answer. The reasons I decided to use different member tables is because there only can exist a trial member when there is a breeder and there can only be a family member when there is a full member. So there has to be a relation between those fields

    Greetings
    Hammie

  4. #4
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    496
    Provided Answers: 24
    it would still be 1 table. Self-relating.
    but you can do it your way too.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •