4
SQL Server is giving me the following warning: "Invalid column name", where the column name has nothing else..
4
SQL Server is giving me the following warning: "Invalid column name", where the column name has nothing else..
3
The flaps of SQL Server Management Studio
work with local cache, so, according to the documentation, use the shortcut keys CTRL+SHIFT+R to update.
Shortcut documentation in English can be found at that link.
Browser other questions tagged sql-server
You are not signed in. Login or sign up in order to post.
With the image it is difficult to read. Put data in text. Preferably additional data to help clarify. Maybe it is invalid because it does not exist in the table.
– Maniero
Just say: Invalid column name 'anoProximaAudiencia'.
– GustavoSevero
I found the question vague, I can not understand if it is error in a query, or table, anyway, if possible explain better.
– MarceloBoni
No, the error is shown in the table itself, when I have open a list of the table.
– GustavoSevero
Can you see now?
– GustavoSevero
select is pointing to the right bank? I’ve happened a few times to be running the query in master instead of my bank.
– Luis Henrique
See if any of these links help you: http://stackoverflow.com/questions/7260487/sql-server-reports-invalid-column-name-but-the-column-present-and-the-quer http://stackoverflow.com/questions/24636025/invalid-column-name-in-sql-server-management-studio http://stackoverflow.com/questions/13840750/invalid-column-name-in-management-studio-but-query-suceeds
– MarceloBoni
But can you run SQL? Because that might just be intelissence showing incorrect information
– Leandro Godoy Rosa
No, a simple query does not work, using this field, because of this.
– GustavoSevero
Worse than no error warning appears when running a system query, just nothing, no results appears.
– GustavoSevero
Yes @Luis Henrique, select is pointing to the right bank. ...
– GustavoSevero
@Marcelo Bonifazio, unfortunately, none of them helped, because they are problems a little different from mine.
– GustavoSevero
Guys, I got it. I had to press Ctrl+Shift+R and restart SQL Server.
– GustavoSevero