If you're just wanting to store a selection of training types, then absolutely. Use a Relational Combo. Store the different types of training in a seperate table and just select which one you want.

If you're saying you are adding more trainings and each of those trainings have many different fields, also yes, use separate tables to store the information on each type of training.

The Many-to-Many video might be of use to you as well.  Richard gives an example of training and certifications in there that might apply to you.

thanks for the reply Adam. Not sure how to tie it all together yet but I think splitting off each training type into its own table is correct. I am a trainer for a company that teach techs How to install and maintain Cisco Servers, Routers and Switches. I have lets say Table A with tech Info then table B,C  tables would be like safety training/Cisco online training/Certifications/other training. I will use the auto number in the Tech table as P. key and would I set a foreign in the other tables from the Primary?

Definitely watch the video above.  Sounds like you really just need one table for training and a second to store they types of training.  The junction would cover your techs.
Many types of training to 1 tech.  Many Techs to each type of training = Many-to-Many.

Ah the way you make it sound now, you just want to be able to assign multiple trainings to different techs?

I would then instead (or also) see that video Scott just linked, make your one table for your Techs, one table for your Trainings, and then a junction table to assign the trainings to the techs and bring everything togethor.

Doing that, you could have like
Tech - Certs
George - Cert 1 / Cert 3 / Cert 8
John - Cert 1 / Cert 4
Jim - Cert 9
Bill - Cert 2 / Cert 3 / Cert 5

72 minutes after the reply we still somehow post at the same time Scott LOL.

Like minds....  LOL