S
spunkymuffmonkey
Hi there,
Firstly, thanks for looking at my message and apologies for being so dumb.
I am having problems designing what should be the simplist of db's. I just
can't get my head around what tables I should have and what relationships any
tables might have.
The database I would like is a very simple reservation system for an
internal training session we run.
The session takes place weekly (normally but not exclusively a Wednesday),
so a table for dates would be needed I think.
There are only 8 places available in each session, would this need a table
of its own related to the dates table?
The only data regarding training session candidates needed would be Name and
Tel#, but how would I relate this to the session places?
Although this is very simple I just cannot work out (not for lack of trying)
the tables and relationships I need and any advice or help would be greatly
received.
Thanks again.
Firstly, thanks for looking at my message and apologies for being so dumb.
I am having problems designing what should be the simplist of db's. I just
can't get my head around what tables I should have and what relationships any
tables might have.
The database I would like is a very simple reservation system for an
internal training session we run.
The session takes place weekly (normally but not exclusively a Wednesday),
so a table for dates would be needed I think.
There are only 8 places available in each session, would this need a table
of its own related to the dates table?
The only data regarding training session candidates needed would be Name and
Tel#, but how would I relate this to the session places?
Although this is very simple I just cannot work out (not for lack of trying)
the tables and relationships I need and any advice or help would be greatly
received.
Thanks again.