Design for membership db (1 Viewer)

[Bentleybelle]

I have put together a membership db for the company where I work. It has about 2000 individual members; members have different membership status, eg student, fellow, etc. They pay different amounts according to their status. Membership has been renewable annually In January – this meant that some members did not get a full year’s membership or potential members would defer.

We are now considering two changes: having two renewal dates, January and July, but membership will still be for 12 mths. And as some members are employees of the same company, we are considering a corporate membership, where the organisation will pay a basic fee, but then individual members may also have to pay something themselves according to their status.

How do I accommodate for these two changes? Should I make a new table for corporate organisations?
Thanks in anticipation

 

[KeithG]

It is hard to give advise if we don't know your current structure.

 

[Bentleybelle]

OK, hope this helps. I have the following tables:

MembershipDetails - containing personal details, join date, status, etc.
Addresses - home and company addresses
Payments - a record of payments made, how much, when, who by (self or company)
MembershipStatus - a look up table
Regions - a look up table
Exams - in-house exams taken, date, pass or fail

I currently enter all this within a form with tabs for membership details, addresses, payments, exams