I would always suggest the use of a form, based on a query first. If you cannot update table(s) based on the query, a form based on it would be useless. To me, forms come after queries where more than one table is involved - unless through experience it's a no-brainer. As for the remainder of your comments, I'm not familiar with your other posts and cannot see all of the fields anyway, so it's a hunch. All the fields can go into the same table regardless, but that may not be the best design either. It would only be a better approach if ALL the fields in your tables were the same in all aspects (not just name, but data type and all other possible restrictions) AND were applicable to one entity. I don't know what that entity is, but venture to say the name you'd be looking for would describe (name the entity) in a way that applies to Alcolyzer and Diacetyl. However, looking again at the other table names, I'm thinking there is no such commonality among all tables, as I don't foresee any commonality between Packaging and Alcolyzer even though the table fields seem repetitive.
I'm thinking you need a primer on normalization (and maybe other things as well...might as well give you all my customary links for newbies)
Normalization is paramount. Diagramming maybe not so much for some people.
Normalization Parts I, II, III, IV, and V
http://rogersaccessblog.blogspot.ca/...on-part-i.html
and/or
http://holowczak.com/database-normalization/
Entity-Relationship Diagramming: Part I, II, III and IV
http://rogersaccessblog.blogspot.ca/...ng-part-i.html
How do I Create an Application in Microsoft Access?
http://rogersaccessblog.blogspot.ca/...cation-in.html
Important for success:
One source about how to name things -
http://access.mvps.org/access/general/gen0012.htm
What not to use in names -
http://allenbrowne.com/AppIssueBadWord.html
About Auto Numbers
-
http://www.utteraccess.com/wiki/Autonumbers
-
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