Our processes include merging some of our queries using the merge operator Sub; query results (static queries) must overwrite an existing query used to assign constituent codes. Web view doesn't allow the use of an existing query name (overwrite). This will add extra or optional steps to our process.
I noticed that this is an issue when running reports that also generate an output query. Not only isn't there an the output query, there isn't even a report. There's no warning that the query name is duplicated with an instruction to create a new name; the report just doesn't happen. I ran a report numerous times before I finally realized that the output query name already existed (which was by design by the way).
Bottom line: we need to be able to overwrite query names.
It would be for all queries not just for merged/static queries. You should prompt as to whether you would like to overwrite the existing query like 90% of other software tools would in that situation rather than simply indicating that the query name is already in use.