If you don't fix the foundational errors (tables design) you will continue to have issues like this. For starters, your form is based on a query join between a non-indexed table field on one side and a calculated (concatenated) field on the other side. You should review db normalization and make sure you understand the PK - FK (primary key - foreign key) parts. In addition, avoid special characters (save for underscore) and spaces in object names, avoid using reserved words (e.g. description). Unfortunately I have to go out in about 20 minutes so I don't have time to see if your current issue can be fixed. In the meantime, here's some links that will help immensely should you choose to study them.
Normalization Parts I, II, III, IV, and V
http://rogersaccessblog.blogspot.com...on-part-i.html
and/or
http://holowczak.com/database-normalization/
Entity-Relationship Diagramming: Part I, II, III and IV
http://rogersaccessblog.blogspot.com...ng-part-i.html
How do I Create an Application in Microsoft Access?
http://rogersaccessblog.blogspot.com...cation-in.html
Important for success:
Naming conventions - http://access.mvps.org/access/general/gen0012.htm
https://www.access-programmers.co.uk...d.php?t=225837
What not to use in names
- http://allenbrowne.com/AppIssueBadWord.html
About Auto Numbers
- http://access.mvps.org/access/general/gen0025.htm
The evils of lookup fields - http://access.mvps.org/access/lookupfields.htm
Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp
About calculated table fields - http://allenbrowne.com/casu-14.html
About Multi Value Fields - http://www.mendipdatasystems.co.uk/m...lds/4594468763
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.