Selecting from one list box to another

[Sonja A]

I have a form which is used to input information for projects. I want to put a list box on the form that shows all employees. I want to be able to click on employees to select them, them move them (with the click of a button or by double-clicking them) to an empty list box (All employees that will work on the project). I also need to be able to remove employees from the project.
Any suggestions?

 

[Pat Hartman]

The employees assigned to a project need to be stored in a relation table. This table implements the many-to-many relationship of people-to-projects. If you use a subform rather than a listbox, you can manage this data without any code.

I've included a sample db that should help you.

 

[Sonja A]

Pat, thanks for the information. I tried to do this, but I am unsure which fields to use in the other table. I can use ProjectID and EmployeeID, but in your example, there is a BookingDate - I don't have such a field I can use. I will be assigning more than one employee to a project, and each employee can be assigned to more than one project so it is a many-to-many, but what can I use to tie them together?
The ultimate goal is to be able to assign and unassign employees to projects. Once employees have been assigned, we will forecast how many hours that employee will spend each month on a particular project.
The employee will also fill out a form where he/she forecasts how much time they will spend on a certain project only for the current month. The manager will compare what he/she forcasted against what the employee estimated and will either accept or reject the changes.
That is the ultimate goal - but right now I am still on the adding an employee portion. I am normally fairly good with Access, so either my brain does not want to function, or what we are tyring to do is above me. I am not ready to admit that though. So any help that you can offer is greatly appreciated.

Sonja Confused and determined

 

[Pat Hartman]

The example db has "intersection" data. That is data that relates to the intersection of the many-to-many relationship. In the sample case, that would be booking date. Sometimes the intersection data is just an ordinary data field such as grade (the intersection of class and student). Booking date serves as a third key in this relationship since the same venue may be booked many times to the same customer but only once on a given date.

Your relationship may or may not have intersection data and the intersection data may or may not need to be defined as a third field in the primary key.