Howzit
Personally, I never have lookups in tables (and a lot of users of this forum are of the same mind) as it makes it a lot harder to troubleshoot potential problems - such as these. I only put lookups in forms that will show exactly the same data as you want to see in the table. But iat the end of the day it is your choice as the developer
The lookup for the manufacturer id doesn't actually work, as
- your manufacturer id in the "manufacturer Id #'s" table is a text field
- the corresponding field in the "sales record" table is a number field
- so when you make a selection it stores the numeric equivalent of your manufacturer id in the this field - not possibly what you expect
- you can see that by selecting a manugfacturers id you already have in this table and it will not open the combobox at the correct record, but at the top of the list
- you can only then join back to the manufacturers table by rebuiding the id by adding zero's in a query
The solution (on the basis that you want to keep the lookup in your table) is to change the manufacturers id in the sales record table to text and make it the second column in your combobox row source (if you keep it 3rd as it stands the manfacturers name will be visible in the table, although it will not be the value stored.
My solution would be to remove all lookups in the tables and only use in the form and ensure that the corresponding values are of the same data type
In regards to your table \ field names etc, I would strongly recommend that you remove any spaces \ special characters from these fields as this will again make potential query \ vba coding more problematic