normalazaing thses attributes

[mil1234ail.com]

I am finding great difficulty in normalasing this set of data:
memberID
memberName
memberSurname
memberAddress
memberTelNO
memberRegion
memberCounty
candidateID
candidateName
candidateSurname
candidateAddress
candidateTelNO
candidateRegion
candidateCounty
candidateElectionType
candidateStatus
-1 thing i want to put in perspective is that all candidates are members and therefore i'm quite confused if name,surname,address etc are to be written each time
ANY help is kindly appreciated....!!!

[JeanWM]

[alf-admin]

Unless you say something about what it should be used for/what is the problem in question, then there is no answer.

I think I understand what you need, and there's no big problem in modeling it, but you are just throwing out some attributes in stead of explaining what you need/what is the issue. Be clear, in plain wording.
_________________
All the best,
Alf
Forum Admin
Light travels faster than sound: That's why so many people appear bright until you hear them speak...
www.databasedesign-resource.com
The Database Normalization eBook

[mil1234ail.com]

Thanks for both of you who answered this question.The 1st person who answered posed me with a good question__what is the difference between member and candidate...and this realised me that what i needed to do was an attribute like eg.memberStatus in which in it i described if a member is a normal one or else is a candidate.All other attributes are he same for both member and candidate...

Thanks.........................

[JeanWM]

If you have one table with the members, candidate will be a possible attribute of the entity member.

A simple kind of 'status' field would be enough to cover this.

Hence you do not need all the fields for the 'candidate'.
_________________
JeanWM - Moderator
Dar síntomas erróneos, resulta en soluciónes erróneas.

[tomylee1]

quite better attribute.
_________________
Meeting Agenda Templates |Flyer Design Templates