that's a "feature" of procedures, with deferred name resolution.
there's no way to turn it off, unfortunately, as it would be very valuable to be able to do that in some cases.
this thread on stack exchange has a lot of ideas
http://stackoverflow.com/questions/4315861/why-does-microsoft-sql-server-check-columns-but-not-tables-in-stored-procs/4315884#4315884 and work arounds, like setting WITH SCHEMABINDING on the procs, but depending on your environment and whether you are "alloweD" to change the procs in that way.
Lowell