would anyone help please?

[mmuk27]

hi guys, as its my 1st post, can i say good looking and popular forum!

What i t is, my friend owns a small local gym. And at the moment he does everything on pen and paper. I want to get back into using microsoft access i used it a bit doing my a levels in school. So i thaught id use this as a 'project' to get back into it, whether he uses it or not.

Im looking to create a database to manage members.

The details stored would be

Member Name
Address
Telephone number
Join Date
Medical Problems


Also, is it possible to control the members who sign in daily, and use that information to have say a member attendance type of section aswell?


Any help would be greatful, but it will probably b a long project as i want to learn as much as possible form it.

Thanks for any replies.

 

[Brian1960]

Hi, Welcome to the Forum. First thing is to learn that you'll get more help if the subject is desciptive not general. "Help" means nothing, "database design issue" is more likely to get noticed.

In a project like this I always start with a list of all the possible data i am likely to want to store. You can then begin to deign the database. Checkout Normalised Databases in this forum.

tblMembers
intMemberID autonumber PK
chrTitle text (from a lookup but not worth having as a FK)
chrFirstname
chrLastName
DtJoined
DtLeft
txtLeftReason

tblAddress
intAddressID PK
intMemberID FK
intAddressType (type of address lookup to address types Home, Business etc)
chrAdd1
chrAdd2
chrAdd3
chrPostCodeZIP
dtEntered
dtLeft (to track old address details)

tblTelephone
intTelID
intMemberID FK
intTelType (as address)
chrTelNo (must be text)
dtEntered
dtLeft

tblMedicalIssues
intIssueID PK
intMemberID FK
dtEntered
IssueDetail

You can logg all entrances so that you can build better marketing plans for members.
You can run graphical analysis on members per day (of the week) to look at your staffing.
Run it per member to see if a member could have a better value membership in line with their useage. (Good way to keep members).

tblLogging
intMemberID FK
dtEntered


Hope this gives you a strat.
No doubt there will be ideas thrown and confusion sewn!

Good luck.