Sorry for the misunderstanding!
I am using jobs as a general term for work request. All Work Request numbers are unique. When I say Job, it's because each work request also has a job# that is not unique. We have multiple districts(Longview, Shreveport, Texarkana, etc.) and they each have their own job#s. So there is a Longview Job# 1 and also a Shreveport Job#1, we don't have a separate "Jobs" table. The job# isn't anything that has to be messed with in this particular situation; i just used it out of habit.
Currently, the "Teams" table basically holds shells where we can edit the technicians and work requests on a day to day basis. The teams are: ALPHA, BETA, CHARLIE, etc.. One day, Team Echo could have technicians, john and jane, and work requests, 61254638 and 71555643, and then a separate set of technicians and work requests the next day. I have any easy way of taking jobs off of the team using an embedded report of the related Work Requests in the team record with a URL button in each row that clears the value in the field "Related Team" but I can't do the same with adding work requests to the team. A team will only ever have up to 10 Work request assigned to it at once, so removing them is not that hard, but we have over 3000 work requests total, so adding from an embedded report would be a nightmare. That's why a simple list with a button would be most efficient.
For this particular case, our field manager will go to the "Teams" table, click on team "Echo" then assign field technicians to the team then enter in the list of work requests he wants that team to work and click the "Add Job" button to have those work request linked to that team by automatically changing the value in the field "Related Team" in each of the listed Work Requests.
