Re: Structure/Relationship Question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi again,

I forgot to ask how I factor in that only a limited number of places are
available for each training session. The maximum amount of places available
is 10.

If you could give me a pointer on how to factor this in I would be very
grateful.

Kind regards

"Allen Browne" wrote:

Does one person only ever attend one session?
Or might they do several?

The following assumes that a person could attend multiple sessions.

Session table (one record for each date), with fields:
- SessionID AutoNumber primary key
- SessionDate Date/Time

Client table (one record for each person), with fields:
- PersonID AutoNumber primary key
- Surname Text
- FirstName Text

Attendance table (one record each time a person attends a session):
- SessionID which session
- PersonID which person

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"spunkymuffmonkey" <spunkymuffmonkey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:C33117FC-8E08-43A7-A6FD-6C530F6865EC@xxxxxxxxxxxxxxxx
Hi there,

Firstly, thanks for looking at my message and apologies for such a basic
question.

I am having problems designing what seems 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 weekly training session we run, the training course teaches the
same thing weekly, only the candidates change. The session takes place
weekly (normally but not exclusively a Wednesday), so a table for dates
would
be needed I think. The course is the same week

There are a maximum of 10 places (altho 8 is the norm) 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,
Position 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 relationship, I have tried a few permiatations but quickly
get in a muddle without the desired result. Some advice or help would be
greatly
received.

Thanks again.


.

Relevant Pages

  • Re: Referential integrity in many-to-many?
    ... there is an Employees table ... every time a training session is logged. ... >in tblEnrollment that doesn't exist in tblEmployee. ...
    (microsoft.public.access.tablesdbdesign)
  • Junction table question
    ... minute unscheduled session at a supervisor's discretion. ... I have an employee table, a training session ... Every explanation I have seen of junction tables seems to ...
    (microsoft.public.access.gettingstarted)
  • Structure/Relationship Question
    ... internal weekly training session we run, the training course teaches the ... The session takes place ... The only data regarding training session candidates needed would be Name, ...
    (microsoft.public.access.modulesdaovba)
  • Basic Relationship Question
    ... internal weekly training session we run, the training course teaches the ... same thing weekly, only the candidates change. ... The session takes place ... The only data regarding training session candidates needed would be Name, ...
    (microsoft.public.access.modulesdaovba)
  • Re: Structure/Relationship Question
    ... To design the data structure to a max amount of records ruins the ... normalization. ... Session table, ... internal weekly training session we run, ...
    (microsoft.public.access.modulesdaovba)