Of course that is the problem.

That's the main reason that we encourage the practice of explicitly 'naming'
the desired columns in every query. Most of us here constantly tell folks
that using "SELECT *" is inappropriate and places the queries in jeopardy of
failure (or producing inappropriate results) in the future.

If all of your queries were properly written, and listed the columns
desired, queries would not fail as a result of adding a new column, or
changing the column order. They just wouldn't deal with the now missing
'new' column and could be corrected as needed.

Also, good programming practices REQUIRE that you never change existing
procedures in a way that will 'break' other functionality. In the rare
circumstance where it is necessary to deliberately break existing
functionality, a complete test regimen and user acceptance cycle must be
invoked again.

There is no 'quick fix' for your problem. You have no alternative but to
manually find and repair all queries so affected. And in the process, you
may inadvertently 'break' other things. As the tag line below indicates,
chalk this one up to 'experience'.

--
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


[quoted text, click to view]