>Recently, I have created a thread in regards to the "Failed to enable constraints" message I was receiving. Later on, we found that this was related to some bad data. However, it is possible to receive that message even if the data is ok. What is more weird in all this is that I do have this message from my application but not from the SSMS interface. If I execute the same SQL command from SSMS, it works. Someone mentioned about a potential setting that could be in effect in one place and not in the other. Is there someone who knows more about that?

In SSMS try to change the settings I mentioned (SET ANSI_NULL and ANSI_NULL_DEFAULT) until you get the same error as from your application. Then you would know which setting to change from the application.