The CustomerID field should get the ID automatically because of the Parent/Subform relationship.

First, thankyou VERY much for responding. I appreciate your help.

In this case, it is not working. I have two other similar subforms that work just fine. This one I created without the wizard.

I get the following error when I try to add a record: " The LinkMasterFields property setting had produced this error: 'The object doesn't contain the Automation object 'Contact.''

I looked at that attribute at the ohter forms that ARE working and they are blank, as is this one.

I uploaded my form showing the LinkMaster/ChildFields and the error message. I have two other form/subform situations with the same master and different sub-records that work fine. Their fields all look the same.

There is ONE other difference between this form and the others. This form was created from a query because it needs to bring in the address for the contact:

"SELECT Contact.*, Properties.HouseNumber & " " & Properties.DirectionPrefix & " " & Properties.Street & " " & Properties.StreetType & " " & Properties.DirectionSuffix & " " & Properties.SuiteNo AS Addr1, Properties.City & ", " & Properties.State & "  " & Properties.Zip AS Addr2, Contact.key
FROM Contact INNER JOIN Properties ON Contact.Key = Properties.Contact_Key
WHERE (((Properties.PropertyType)="primary"));"

I think the problem may be the dot (.) in the field name for the Link Master Fields.

The above message relates to the MAIN form to which the SUBFORM is related. I don't think I made that clear.

Thanks for that suggestion. The full name of the field is <tablename>.<field>, which in this case is "Contact.Key" I removed the "Contact." part, and when I saved it, access rewrote it to "Contact.Key". I think that must be because the initial data was from an INNER JOIN including another table. But, I really don't know. It is obviously trying to "help me out" somehow, but I can't figure out what.

When I click on the three dots it brings up the "Subform Field LInker". The pulldown list provides me with "contact.key" on the Master side and "contact_key" on the Child side, resulting in the same settings. Still, I get the same error.

Very mysterious.

I figured it out. Thank you, Kevin, for making me look elsewhere. I had added a redundant reference "contact.key" to the SQL SELECT statement earlier to try to fix something. When I removed it, then the field "Key" was presented in the "Subform Field Linker" pulldown. I used that, and everything worked.

Very Grateful,

Jim

That's great. Glad you got it working.