If my proposed description matches what you are working with, then you'll
want to consider a table structure that allows for each of those entities
(person, event, workshop, topic) AND another table (or more than one) that
lets you relate these (e.g., Registration).

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Phil" wrote in message
news
Yes thats right, my existing database already handle bookings for multiple
events, I am really struggling to add workshops to it, I thought I had it
until we ran an event with two workshops

Thanks

Phil

"Jeff Boyce" wrote:

Phil

We might be focusing to narrowly on 'tables' and not enough on the
entities
and relationships. The tables will follow if you've laid out (usually
pencil/paper) the entity/relationship diagrams.

It sounds like you are saying:
* one person can register for one-to-many events
* one event can have one-to-many workshops
* one workshop can have one-to-many topics
* one person can register for one-to-many topics

Does this match your situation?

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Phil" wrote in message
...
Hi Jeff

Thanks for your reply, you have it correct with the workshops, although
the
attendees are first registered on an event and then chose which
workshop
they
want to attend. I have added a workshop table and did use a field in
the
registration table to store what workshop they want, the problem is
that
means they can only have one workshop for each course (unless I am
missing
something as they only have one registration record for each course).
The
other issue I have is that if an event has two workshops they may be
different workshops

e.g
am
Lung cancer
clorectal cancer

pm
breast cancer
kidney cancer

how do i account for that?

Hope you can help

Phil

"Jeff Boyce" wrote:

Phil

It sounds like you are saying one Event can have zero, one, or many
Workshops, and that Attendees are registering for Workshops rather
than
Events.

If you add a Workshop table, then use WorkshopID in your
trelRegistration
table, would that do it?

Regards

Jeff Boyce
Microsoft Office/Access MVP


"Phil" wrote in message
...
I have an events database that I now need to add workshops, the basic
structure of the tables is

Events:
---------
EventID

Attendee:
-------------
AttendeeID

Registration:
--------------
RegistrationID
EventID
AttendeeId

the real world situation is that some events we run have workshops,
normally
the group will split into smaller groups and attend one of the
sessions

e.g.
Bereavment
MCA
Cancer

Each event may have more than one workshop in a day, one workshop or
none
at
all. I have no idea how to design the table structure, do I need
seperate
tables for Workshops, sessions. Any advice would be greatly
accepted.
If
you need any more info let me know

Thanks

Phil