Many-to-Many

Many-to-many is what I thought, but it dawned upon me that if I want to assign two staff people to a single client, would that not be a many to one relationship?

I see the problem. I need to select a family to be audited by two staff members. I have a FamiliesT, a StaffT and I need a third table that selects which family will be audited and then to select two staff members to be the auditors. I built another table, FamilyAuditT. The problem is, after several attempts and using different combinations of relating the FamilyAuditT, I can only select one staff member because I am bound to the StaffID. I have two choices. 1) use lookup fields or 2) duplicate the StaffT , call it Staff2T and then use a Combo Box to select a staff member from StaffT and Staff2T. The problem is that I have to update both Staff tables with staff changes, which obviously is a not acceptable. I am sure the right VBA code will solve this problem but I don't know what that would be. Alternatively, is there a way to edit both StaffT and Staff2T simultaneously?

If your requirement will not change in the future, to assign more staff to a customer then the simplest solution is that you have staff ID1 and staff ID2 on the customers table. Then in your query, you would link a customer table 1 to 1 to the staff table. You will need to iterations of the staff table.  
This is not considered good design as you will be limited to only two staff assigned to a customer.

You do not need 2 staffT tables. You can link your customer table to the staffT twice.
To Show you this, create a new query add customerT once and add staffT twice.
You will get the second stuff table renamed staffT_1. Now link staff1ID from the customerT two staffT and link staff2ID from customerT table to staffT_1.

Add the following fields to the query; customer ID, customer name, staff ID and staff name from staffT, staff ID and staff name from staffT_1.
I think this will give you what you are looking for
Good luck

Thanks, all, this jarred my memory.

I remembered I built an Access file awhile back with junction tables and forms that I can now use as templates. Access is not like riding a bicycle. Use or lose it. At least for me.

"it dawned upon me that if I want to assign two staff people to a single client, would that not be a many to one relationship?"

Just to back up a bit and help you talk it through.  
Each Staff can have many Clients.  Each Client could be serviced by many Staff members. So the many-to-many
You can limit it to two but if in the future your requirements or needs change you don't have to change all your forms by setting it up like Kevin showed above.

If you do want to limit it to only two see the Event Enrollment video for an example of how to do that.