A workaround for those curious, simply create a view of your statement as suggested by MSDN, like so:

CREATE VIEW GetAroundSQL2005AnnoyingReadOnlyFeature

AS

SELECT Player.FirstName, Player.LastName, Team.Name

FROM ...

Right... I don't use proper ETL practices for my test environment when debugging. Once I find what's wrong I can write up an ETL to fix the problem on production...

I doubt we are alone here, the great thing about forums is that there is always some odd, esoteric reason something that is different is acceptable. When programming, I edit...

Where in SSMS can you go to edit cells that are a result of multiple tables?

For example, if I open SSMS and right-click a table called Player then select Open...

How sad, I used this feature of 2000 quite heavily. Has anyone found a fast workaround?