Tuesday, March 29, 2011 12:59 AM
I am having trouble with VS 2010 not throwing an exception when an error occurs during a sql server transaction. As a simple example, If I run the following code to insert a value into a table in SQL server, it runs through the code without error even though the column name is Period not Perioda. In past set ups it would have complained that Perioda is not a field. I'm thinking something must have changed in my debugger settings but I can't find anything that would cause that.
string sql ="Insert Into Table4 (Perioda) SELECT 255";
SqlCommand sqlComm = new SqlCommand(sql, conn);
sqlComm.BeginExecuteNonQuery(); //Would normally error here but steps over code as if it executed properly and moves to next line.
Thanks in advance for any help.
- Moved by Jon Langdon Tuesday, March 29, 2011 3:01 PM (From:Building Development and Diagnostic Tools for .Net)