Christian Buettner-167247 (12/16/2010)
This error is raised all the time, and also when you switch the table to which you add this extra column. To me this is a strong indication that this error is not "undefined".Pls let me know your thoughts
I think you're right. The BOL article clearly states:
However, for modifications to resolve to the table that was created in the nested procedure, the table must have the same structure, with the same column names, as the table created in the calling procedure.
So, if the tables have the same name but different structure, any inserts, updates, and deletes will fail with an error.