Cool.

Hey Mike, here's an interesting article about this error and general reasons, FWIW:

http://sqlserver2000.databases.aspfaq.com/why-do-i-get-object-could-not-be-found-or-invalid-object-name.html

>Ok, I have found the reason. One of the new inserted table contains some fields that I have not passed with the proper name. It seems the script analysis the code before executing in it. In this case, it detected that a linked server import table didn't contain the proper field name and returned that code. So, basically, on that verification, it is entirely done before the first line of script is even executed.