Hi Deborah

can you use VBA?
Are familiar with Recordsets?

I am familiar with VBA but and not very good at it. I have followed some of these videos with limited success.  
I was thinking maybe if i put a button to click after entering the top of the form to load that info into the table then macros to append the selected customers to the table for that record.....  somehow????

OK...  See staying up all night playing with access is not always a good idea.  I may have just thought of a pretty simple solution.  will see if it works and let you all know.

It is not ideal but it works and is pretty simple.  I went back to the ContactXCustomerT and made the CustomerID a lookup field to the CustomerLFQ and allowed multiple selections.  Then Went to the Attendance form which is based on the ContactXCustomerT and just added the CustomerID field to the form.  It is working .....  fingers crossed as I have no idea what adverse consequence this may lead to.

Good luck

Well that screwed everything else up.....

Run-time error '3831':
The Multi-valued field 'CustomerID' cannot be used in a WHERE or HAVING clause.
I have to go undo a bunch of stuff

You need to use the .Value property to reference individual values.  E.g.:

     SELECT Field1, Field2, CustomerID.Value = 1234

The above finds records in which the multivalued field CustomerID contains 1234 as one of its values.

Multivalued fields are hard to handle, cumbersome to design and code for, and is unique only to Access and cannot be carried over to other database systems like SQL Server, should you ever need to migrate from Access to SQL Server like many Access users have done.  If you are a beginner as your badge indicates, I don't advise you using them at all until you become really proficient in Access.  Richard strongly advises against them too.

I forgot the WHERE keyword:

     SELECT Field1, Field2 WHERE CustomerID.Value = 1234

Thank you for the help.  The multivalued field select was a big failure.  I will use a continuous subform from an X table within the single related form.  It is not what I envisioned but works well enough. Thanks again for the help provided.