spartansFC
Programmer
Hi
So i've been asked at work to create a new database, i've created many in the past but thought i'd get a few ideas from people as to how to best create a good design both in tables and relationships. I think i might need a many to many relationship which i sort of know how to do but... anyways here's what i need to do:
The database is basically a family unit for a play scheme (out of school clubs etc) so i need to record:
all the members of the family
each family member might have a different address
i need to keep a record of each parents employee details
I did think about using:
tblFamily
lngFamilyID
tblParent
lngParentID (PK)
lngFamilyID (FK)
strParentname
lngAddressID
tblAddress (many to many)
lngAddressID
lngParentID
lngChildID
tblChild
lngChildID (PK)
lngParentID (FK)
So i think i could use the above tables and link them via the respective foreign keys. This would allow me to have each family member could live at different addresses etc.
I also need to keep a record of each parent's employee details.
Is there also a way of copying and inserting an address into another family members details? Say if there was 10 people in a fmaily, i don't want the user to have to type in the address 10 times, so maybe a command button that inserts the main family address into the record.
So is the above table design a good place to start or pretty bad design?
Mikie
So i've been asked at work to create a new database, i've created many in the past but thought i'd get a few ideas from people as to how to best create a good design both in tables and relationships. I think i might need a many to many relationship which i sort of know how to do but... anyways here's what i need to do:
The database is basically a family unit for a play scheme (out of school clubs etc) so i need to record:
all the members of the family
each family member might have a different address
i need to keep a record of each parents employee details
I did think about using:
tblFamily
lngFamilyID
tblParent
lngParentID (PK)
lngFamilyID (FK)
strParentname
lngAddressID
tblAddress (many to many)
lngAddressID
lngParentID
lngChildID
tblChild
lngChildID (PK)
lngParentID (FK)
So i think i could use the above tables and link them via the respective foreign keys. This would allow me to have each family member could live at different addresses etc.
I also need to keep a record of each parent's employee details.
Is there also a way of copying and inserting an address into another family members details? Say if there was 10 people in a fmaily, i don't want the user to have to type in the address 10 times, so maybe a command button that inserts the main family address into the record.
So is the above table design a good place to start or pretty bad design?
Mikie