table layout for drag racing

[Guest]

Hi,

Can anyone look at this database design and help me out.The purpose of this
database will be to store race results for drag racers this will include
specifications of there cars, car setups, engine specs, track conditions and
weather conditions. The main people to use this database will be drag racers.

the main use of the database will be to look up car and engine setup from
previous meets by air temp humidity relative altitude and set the car and
engine up similar as to keep the cars elapsed times consistent through out
the year.

Everyone is free to use or modify the design.


event (table)
eventid (autonumber pk)
eventtype
eventdate

driver (table)
driverid (autonumber pk)
firstname
lastname

car (table)
carid (autonumber pk)
carmake
carmodel
enginemake
enginesize
gearbox
diffratio
tyretype
tyresize
tyrepresshot
tyre presscold
carbymake
carbysize
jetsfront
jetsrear
fuelpressure
basetiming
totaladvance
enginecompression

cardriver (table)
cardriverid (autonumber pk)
carid (unique index fld1, foreign key to tblcar)
driverid (unique index fld2, foreign key to tbldriver)

track (table)
trackid
relativealtitude

weather (table)
weatherid
racetime
tracktemp
milibars
humidity
airtemp

results (table)
resultsid (autonumber pk)
cardriverid
racetime
stagerpm
shiftrpm
reaction
60fttime
330fttime
660fttime
660ftmph
1000fttime
elapsedtime
elapsedmph
comments

Any info would be greatly appreciated

 

[Jeff Boyce]

Dean

Just a small comment from a quick scan through ...

Your Car table seems to imply that a vehicle is set up only one way (e.g.,
tire pressure, tire type, ...). Or, at a minimum, you "lose" the previous
setup when you write the new one.

I suspect you want to create a 1:m relationship -- one car, many setups.
Perhaps the "setup" is closely related to individual runs?

Good luck

Jeff Boyce
<Access MVP>

 

[Guest]

Thanks for your reply,

I have actually done a lot of mods since i posted, The car and driver table
now have a joint tanble CarDriver.I have divided engine into engine and
engine setup and put these also to a joint table EngineDetails.You can view
the latest database at

http://www.dfwcomputer.com/mick/draglogger.zip

Thanks...