@JHB,
This sounds like a great idea that is hopefully going to save me lots of time and tears!
I have a few questions if you don’t mind:
1. It looks like every time the “make a table” query is executed it overwrites the previous table, correct?
Is there a way to suppress all of the prompts and warnings?
Also, it would make sense to limit this table to a subset of data. One of the fields present in the “make a table”query is the project name “project_name”. Is it possible to set that parameter “project name” from another form, based on the user’s action (If they click on a particular project record)?
2. Also, since the new table is going to be the row source for the form and going to be deleted each time the query is executed, do I need to redefine the row source for the form or not?
3. You’ve mentioned updating the original table via update queries. The user will only be allowed to make changes to three fields, all form the same table “tbl_Variants”. Is "tbl_Variants" going to be updated from the form or the new table that is the row source for the form. Also, how will it know which records to update? Do I tell it to update all three fields for data that belongs to that project.
Thanks, Mila