>>I found the problem! The "wrong" table name was in the Trigger of the SQL Server DB.
>
>My first thought when I read your message was about the trigger, but you told you deleted that table? Did SQL Server still allow you to delete it?
I was trying to delete a row, not a table. And I was confused (I am so busy these days, both personal and work that I can't think straight). And I thought that the delete trigger was not part of the procedure. But it turns out, it is. The fix was easy; simply comment the "wrong" table in the trigger code.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
