Query Editor - Make it smarter for INSERT INTO queries
Currently, if an existing INSERT INTO query has a problem with an underlying query (if there is an error due to a renamed supporting query or table name, for example), the Query Editor inserts new "phantom alias names" into the QueryDef for each column.
So, the resulting SQL looks sort of like this:
INSERT INTO MyTable (ColA, ColB, ColC...)
SELECT MyDerivedColA as Expr1, MyColB as Expr2, MyDerivedColC as Expr3…
FROM (from clause with some underlying table/query naming error here)...
My request is that since the Query editor is "smart enough" to introduce those "Expr#" Alias labels when needed due to errors, IT ALSO NEEDS TO BE SMART ENOUGH TO REMOVE THEM when they are no longer needed (i.e. when the underlying query/table naming error is resolved, and the "Expr#" labels only introduce unneeded confusion/obfuscation)!
Once we "cure" the underlying dependent query/table name issue, IF all the SOURCE column names (once again) MATCH the TARGET column names, Have the Query Editor AUTOMATICALLY REMOVE any of the "Expr#:" alias column names labels it finds.
This is my wishlist request.
Since your Access/Office Roadmap now has an alternative SQL Editor on the list, I would like to renew this request, because once we can actually edit SQL with some REALLY IMPROVED tools and can care about SQL formatting and whitespace (and maybe SQL Comments too?), this issue will drive some folks absolutely NUTS when their SQL gets "messed up" with these EXPR# alias names unexpectedly.