Forum Home
Press F1
 
Thread ID: 94978 2008-11-19 07:37:00 Basic Database help needed bones (10257) Press F1
Post ID Timestamp Content User
721407 2008-11-19 07:37:00 I'm trying to set up a database to help my wife keep records on athletes performance for our local club. ( I have a laptop, makes me a database whiz???)
I want to be able to have each athletes records for their various events, chronologically entered from which I can dig out their personal best. So each athlete will have multiple events with a distance/time history for the season.
I think I have some sort of mental block with the whole process, I just can't seem to "click" on how to do it. Heres (http://www.bws.co.nz) a link to a file thats a small start for one event.
I've read books, googled, tried mystic prayer but I think me, databases, relationships(in databases mainly, but could spread to wife), are never going to be good buddies.:badpc:
Any help appreciated in pointing me in the right direction
bones (10257)
721408 2008-11-19 20:17:00 You using Access? pctek (84)
721409 2008-11-19 21:07:00 You using Access?
Yes.
bones (10257)
721410 2008-11-19 21:40:00 I would probably start by setting up something like this

www.imagef1.net.nz

Athletes details in Athletes Key is their club number which should not change.
Venues, eg Papakura, Pakuranga, Mt Smart etc, with the venue co-ordinators contact details
Events - eg Shotput, Discus, 100m, 400m, 800m etc

Then the Results of each event.

Once this is set up then Various queries can draw almost any details you want from it.

You can even set up forms for easier input into the Tables, and Forms or Reports to print out results or Venues for upcoming events.

You can also set up a roster table for various tasks at your locally hosted venue.
Bantu (52)
721411 2008-11-19 21:47:00 You're definitely on the right track there Bones - all you need to do to link the tables is have a field with is both common to all tables (in your case, the Athlete ID), but cardinal enough that it's unique to every record (or row) in the table.

I don't think you need to have multiple tables for each event type either; I'd just have a 2nd table called Events, and within that a field (column) called Type, where you enter the event (shotput, hurdles, javlin etc)

Having only one other table means that you don't have to keep entering Athlete ID's all over the place.

HTH!! :thumbs:
nofam (9009)
721412 2008-11-19 22:03:00 This all looks promising!. I have a bit of time tonight so will have another bash. I seem to have the basics of setting up tables(mostly) but when I go to do the relationships it nearly always seems to fall over and I get error messages about duplicate records etc. But anyway I'll keep trying. Thanks to all so far.:thumbs: bones (10257)
721413 2008-11-19 22:59:00 bones PM there for you with a link to a database that might help. Bantu (52)
721414 2008-11-19 23:48:00 bones PM there for you with a link to a database that might help.
Thanks Bantu. You have made my day.:clap
bones (10257)
1