hi to all

I'm fairly new at this but making great progress. I'm really struggling
with part of a database I'm working on for a soccer club. Most of the work
is done (contacts, registration, etc) but there is a part of the db that is
giving me tons of trouble. This has to do with timetabling / scheduling.

Basically, kids can sign up for classes that run in a Session (Fall,
Winter, Spring, etc). Some of these classes run once a week at set times
(eg, Tiny Tots), others run multiple times a week at varying times (eg,
Junior Kicks). (this is deternmined by the level and age of the class
members.) To complicate things, there are other higher-leveled classes that
run in a full-year session (eg, Comp Stars A). Finally, there are some
students that sign up for a multi-hour camp sessions that run all on one day.

I'm really not sure what is the best way to relate my tables. I've
experimented with...

a) A master table called tblEvents, that is linked to a number of other
tables. (tblstudent, tblSession, tblClass, tblDates, etc.)

b) A master table called tblEvents that is linked to other tables that are,
in turn, linked to others. (for example, tblEvents links to tblClass, but
tblClass is now linked to tblSession, tblDates, etc.)

Here's my questions:
1) are there any general guidelines or advice from the experts for this sort
of thing?

2) are there any good schemas laying out this type of scheduling situation?
I've been looking without a lot of success.

One of the things that is important to our coaches is that the tables be set
up in such a way that I can easily print timetables for, say, a given week.

much appreciated
Terry