dbTalk Databases Forums  

Database

comp.database.ms-access comp.database.ms-access


Discuss Database in the comp.database.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
PR
 
Posts: n/a

Default Database - 11-09-2003 , 05:31 AM






A charitable burn survivors organisation wants a database. Could
someone help me setting one up(tables - linking tables -one to
one/many etc) on the following information:

A member can be an Association (full fletched with voting rights -
will need to hold details of 2 representatives), a member can also be
a legal person (no voting rights), a member can also be a physical
person (no voting rights) and a member can also be an Executive
Committee member/Association representative at the same time.

Thanks

PR

Reply With Quote
  #2  
Old   
Allan Thompson
 
Posts: n/a

Default Re: Database - 11-09-2003 , 10:21 AM






Assumption: If I understand correctly, someone might be a legal person (no
votng rights) but still have voting rights because they are an Association
representative. If that's the case, I would suggest the following tables:

tblMemberAssociation:
Fields: AssocID; AssocName; [Other Attributes]

tblMemberPerson:
Fields: PersonId, [Person Name, Address, Other Attributes]; AssocID ( link
to tblMemberAssociation; entry not required)

tblPosition:
Fields: PositionID; PositionDescription;VotingRights (Y/N field type)

tblPersonPosition:
Fields: PersonID, PositionID, EffDate, EndDate [Other Attributes if needed]
(One-Many Relationship: tblMemberPerson to tblPersonPosition. PositionID
selected from tblPosition.)

I would include the "Physical Person", "Legal Person", Association
Representative and Executive Committee Member in the Position table /
PersonPosition table. Assigning the voting rights based on position should
make it easier for you to construct queries & determine who has voting
rights, as opposed to doing it at the person or association level. You
will, of course, need a query that joins the MemberPerson, MemberAssociation
(left join from MemberPerson), PersonPosition and Position tables to pull
together all attributes.

Let me know if this design seems to work for you.


Allan Thompson
APT Associates/ FieldScope LLC
MS Office Automation / Measurement and Reporting Systems
www.fieldscope.com
860.242.4184


"PR" <rudy (AT) burnsupportgroupsdatabase (DOT) com> wrote

Quote:
A charitable burn survivors organisation wants a database. Could
someone help me setting one up(tables - linking tables -one to
one/many etc) on the following information:

A member can be an Association (full fletched with voting rights -
will need to hold details of 2 representatives), a member can also be
a legal person (no voting rights), a member can also be a physical
person (no voting rights) and a member can also be an Executive
Committee member/Association representative at the same time.

Thanks

PR



Reply With Quote
  #3  
Old   
PR
 
Posts: n/a

Default Re: Database - 11-10-2003 , 02:32 AM



Hi Allen

I'll have a go on that!! THANKS!!

Rudy

"Allan Thompson" <athompson (AT) fieldscope (DOT) com> wrote

Quote:
Assumption: If I understand correctly, someone might be a legal person (no
votng rights) but still have voting rights because they are an Association
representative. If that's the case, I would suggest the following tables:

tblMemberAssociation:
Fields: AssocID; AssocName; [Other Attributes]

tblMemberPerson:
Fields: PersonId, [Person Name, Address, Other Attributes]; AssocID ( link
to tblMemberAssociation; entry not required)

tblPosition:
Fields: PositionID; PositionDescription;VotingRights (Y/N field type)

tblPersonPosition:
Fields: PersonID, PositionID, EffDate, EndDate [Other Attributes if needed]
(One-Many Relationship: tblMemberPerson to tblPersonPosition. PositionID
selected from tblPosition.)

I would include the "Physical Person", "Legal Person", Association
Representative and Executive Committee Member in the Position table /
PersonPosition table. Assigning the voting rights based on position should
make it easier for you to construct queries & determine who has voting
rights, as opposed to doing it at the person or association level. You
will, of course, need a query that joins the MemberPerson, MemberAssociation
(left join from MemberPerson), PersonPosition and Position tables to pull
together all attributes.

Let me know if this design seems to work for you.


Allan Thompson
APT Associates/ FieldScope LLC
MS Office Automation / Measurement and Reporting Systems
www.fieldscope.com
860.242.4184


"PR" <rudy (AT) burnsupportgroupsdatabase (DOT) com> wrote in message
news:95ed955a.0311090331.15e020f7 (AT) posting (DOT) google.com...
A charitable burn survivors organisation wants a database. Could
someone help me setting one up(tables - linking tables -one to
one/many etc) on the following information:

A member can be an Association (full fletched with voting rights -
will need to hold details of 2 representatives), a member can also be
a legal person (no voting rights), a member can also be a physical
person (no voting rights) and a member can also be an Executive
Committee member/Association representative at the same time.

Thanks

PR

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.