Mike,
I may be wrong about your requirements, but here are my assumptions:
1. You need to keep information about employees, such as first name, last
name, email address, etc. For this you need an Employees table with an EmpID
primary key column, along with additional columns for specific employee data.
2. You need to keep information about projects, such as the project's title
or description, start date, end date, etc. For this you need a Projects table
with a ProjectID primary key column, along with additional columns for
specific project data.
3. You need to keep information about which employees work on which
projects. One employee can work on many projects and one project can be
worked on by many employees.
This is a classic many-to-many relationship. It requires a third, or
"linking", table to establish the relationship. In this case you need a third
table, EmployeesProjects, with an EmpID column and a ProjectID column. These
2 columns will together be the table's composite primary key. This table
could also contain additional information, such as how much time a particular
employee has worked on a particular project.
With this design, if the employee with an EmpID of 1 is working on the
project with a ProjectID of 5 there will be a row in the EmployeesProjects
table that looks like this: 1 5
My point is that you need to get the database design correct up front,
before writing any code or worrying about combo boxes, etc.
Of course, I may be completely wrong in my assumptions about your data needs.
Kerry Moorman