Sounds to me like you should be basing a form on this query (assuming you can edit the query now). Making a table seems like an unnecessary step in that case. Then what? You have to create another query to update the data based on this new table? I don't see how having this table eliminates the need for picking and choosing fields in a query to make it in the first place.
You said there were lots of fields. You didn't say if there were lots of separate updates. If many separate updates I think that just makes the situation worse when it comes to creating a new table. Why not just use a form and either a) directly edit the data if it's updatable or b) have the form unbound and create the sql in vba based on which fields have data? Using a form is more user friendly than getting someone to monkey with query design, IMHO.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.