What causes the “invalid column name” message in an SQL Exception?
This message is given because SQL is trying to write to a non-existent column in the table. Possible reasons for this could be: The field names specified in the foreign reference mapping are not properly specified. The column name is misspelled or in the wrong case. Check the methods where field names are set in the mapping.
Related Questions
- After a message has been moved to an exception queue, is there a way, using SQL or otherwise, of identifying which queue the message resided in before moving to the exception queue?
- What causes the "invalid column name" message in an SQL Exception?
- What causes the "invalid column name" message in SQL Exception?