*(Time 6:45) (i)If you make a Query (based on the relevant Tables), which only has the fields you want to see   that s fine for the Form you make from it  But when end users go to the Form and add new records of data for  just  those fields   wouldn t it transfer back to the corresponding Tables (through the Query) for  only  those fields (and not the rest of the fields)  resulting in new Table records (in each of the underlying Tables) that are incomplete (from not having those other fields  data entered anywhere)? (ii)Then, if you make a new Query or Form based on those Tables in the future, and want to display one of the other fields' values that you did not included in the first Query   wouldn t all of those fields  values show up as blanks for every record (when they could have had a value, if there was some way to specify the rest of the fields  values in the first Query)? (iii)Could we instead somehow make a separate Table from our initial Query that only has those fields from the Query, and make that Table the Record Source for our first Form, so that the data gets transferred there(correctly), and doesn t fracture the original Tables with only  partial-data  records. Is there a way to do this (like, is that what a  Make Table  Query does to get around that issue), or is there another way you might know of around this problem?

---

Reply from Alex Hedley:

It's a design choice you can make.
If you want the Form to be a data entry Form then put the Fields you wish to have values into the Query and show them on the Form, sometimes you might not want to have all the Fields entered, or the Form might just be for display purposes so you don't need to show the IDs or other unnecessary values.