Deleting SQLCommand throwing inadequate exception

Question

I have virtual dataGridView which displays all values in table by Just-In-Time method documentation here. My view has more computed columns, so I use it only to show data and then only delete by single SQLCommand. The problem comes when I am executing the delete command. When I execute it, it throws error

Conversion failed when converting the nvarchar value 'TextValueFromThirdColumn' to data type int.

xxx is not ID, but computed data in third column.

using(SqlConnection c = new SqlConnection(Properties.Settings.Default.ConnectionString))
     {
          c.Open();
          SqlCommand command = new SqlCommand("delete from entryTable where ID = @id", c);
          command.Parameters.AddWithValue("@id", dataGridView1.SelectedRows[0].Cells["ID"].Value.ToString());
          command.ExecuteNonQuery();
     }

As you can see I am building query with parameter which adds just fine, but the error thrown seems inadequate for me, because third column has nothing to do with my ID column. Thanks in advance for any advice

Can you just change it to this: Convert.ToInt32(dataGridView1.SelectedRows[0].Cells["ID"].Value.ToString()) — McGaz, Aug 24 '16 at 16:18
i think you have set the `ID` as your primary key, I dont think it allows your to delete it, but you can `REPLACE` it I believe., if not maybe you can change your `ID` column to an INT that have auto increments on, so that you dont have to manually add the int key. — user1234433222, Aug 24 '16 at 16:23
@McGaz the ID adds fine, as you can see in the screenshot, I don't think this is problem with parameter. Now when I tried it, it throws the same error — Hynek Bernard, Aug 24 '16 at 16:24
@Werdna Nope, the `ID` column is just `Identity(1,1)` and primary key is another 2 columns — Hynek Bernard, Aug 24 '16 at 16:25
It already is `int`. I don't think it would even allow me to make any other datatype autoincrement. — Hynek Bernard, Aug 24 '16 at 16:27
@McGaz sorry to bother you, the code works just right. Check answer for details. — Hynek Bernard, Aug 24 '16 at 16:35
No worries, just checking things out whilst my code builds. Glad its working — McGaz, Aug 24 '16 at 16:37

score 0 · Accepted Answer · answered Aug 24 '16 at 16:33

Okay, It was my dumb fault. This is problem with trigger on SQL server. I did not realize I made changes to database layout and trigger stopped working because it inserted values into wrong column. The error code showed what happened with trigger, not with row.

Deleting SQLCommand throwing inadequate exception

1 Answers1