Interesting...
Please post your full code causing the errors, including DDL for all the tables needed, and the scripts needed to populate at least a few rows into each table. I can't think of any reason why you cannot insert data into a temp table and then immediately JOIN to it unless you are using table variables, or you have something running outside the scope if the particular spid running the SELECT <<>> INTO.
I get the error ANY time I create a new table and try to reference that table in the same transaction. Semicolons don't fix it, but GO statements do. Whether I use temp or permanent tables doesn't matter.
Are you instantiating an actual transaction somewhere?
I found it odd (and possibly very revealing for those who know what happens behind the scenes) that Activity Monitor immediately produces the same error, as though it's opening generates a table it reads from.
It is weird that you would notice any error in the Activity Monitor as a result of this...
I cannot reproduce this...unless someone has come across this (which I still think is a SQL configuration issue) we will need DDL and some sample data to test...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience