>>>>If only one table is used in a query, why do you need to use table's name referring to its columns?
>>>>
>>>>Also, could it be case-sensitive installation of SQL Server?
>>>
>>>:-)
>>>This is an example, not the full query.
>>>No, nothing on this server is case or accent sensitive.
>>
>>For multi-table queries I normally use aliases so never faced this problem.
>
>Usually me too :-)
>but sometimes I forgot and on my computer queries work.
>That is why I want to turn tis off so, on my machine they bomb as it should be :-)

Do they always get the error on specific query or any query with this pattern fails?

See if this thread can somehow shed some light

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/3b2e0875-e98c-4931-bcb4-e9f449b637d7/the-multipart-identifier-aliasfield-could-not-be-bound?forum=transactsql

(e.g. field name as as table name).

It may also do something with the schema.

Try also these google keywords:

"always qualify schema name tables SQL Server"

I got several interesting results, but simply don't have time to read them all. In fact, I wanted to go to JCC to exercise 20 minutes ago but instead reading UT and eating :(

BTW, just in case I tried query in the first manner and didn't get any error (nor I expected any).