Feilds and Junction Tables the Agony

[Guest]

I am starting a data base from scratch for a library of thousands of
video tapes. The company I work for is broken up into many different
departments and groups. The videos need to be sorted into the appropriate
category for which I created a combo box field with the names of the
different departments. The fields that accompany them are mostly the same
(Date, Program
Title, Footage Type, Agenda and the big one which i assigned ten separate
fields for, SPEAKERS).
Earlier it was said that I sould create a new table for speakers but I am
totally confused as to the layout? I know that any given video may have many
speakers (if so do i need a field for each speaker or do they get their own
record?) and that I need to be able to reference all the videos one person
made a speach at and what speakers are on a perticular video?
Should their be a table for the program names them self? How many
tables do I need to do this?
In the end to keep this monster together and orginized I need a way to
have everything divided into the categories. Because their are so many
categories the tapes can't just be labled 1,3,4,5 or they would all just get
grouped together. Instead the department has it's own section on the shelf so
what I want is a key that identifies the department and the tape number
starting with 1 and going up for each department.
Is this possible? and if so how can it be done?


Can anyone help?
Can anyone help me? AAAHHHHHUUUUGGGGGHHHH the pain!!!!

 

[[MVP] S.Clark]

The VideoSpeakers table would be a child to the Videos table.

VideoSpeakerID (Autonumber PK)
VideoID (FK to Videos table)
SpeakerID (FK to Speakers Table)

To get fancy, you could add a SpeakerRole. (Primary, Secondary, Cameo, etc.)
to the table.