What you need are two separate tables: one of classes and one of jobs. Each one should have a PK. Now you need a separate combined table. This table will contain the pk from jobs and one course pk from the classes. Each required job/class combo must be a separate record for normalization reasons. All you need are the two fields in each table.
Let me see if I got this right. 3 tables
Job positions = PK, Title
Classes = PK, Class name
Combination table = PK, TitlePK1, ClassPK1 (3 columns?)
PK, TitlePK2, ClassPK1
PK, Title PK3, ClassPK1
PK, Title PK1, ClassPK2
PK, Title PK2, ClassPK2
PK, Title PK3, ClassPK2 .....etc
Or is it: PK, TitlePK1+ClassPK1 (2 columns)
Like this? Sorry, just having a hard time wrapping my head around these. Not sure I'm thinking in the right direction.
I would say that the combo table doesn't need a pk of its own.
Each pk in the combo table is a separate field, such as ClassFk (that's foreign key. In its local table it's called primary key; in a 'foreign' table it's called foreign key.) and JobPosFk.
By the way, you can also adjust your employee table, which already includes a field called 'job position,' to reflect the job position table's pk instead of a long-hand text description which is subject to data-entry anomalies such as added spaces or punctuation, numeralization (such as '1' instead of 'one'), spelling errors, etc.
Thank you Sam.
Whoop! Worked like a champ. I used my employee table for job titles, as it was already built and included. Did however build the combination table with a PK - before I read this last post of yours. I assume it's still okay, just unnecessary?