>>>>>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.
>>
>>As far as I understand, you try to alter (SQL UPDATE, in DBX REPLACE) the value of a field that you use for something like deleted, not delete a column?
>>
>>There is a way to update a SQL Server that is called Delete and Insert - First delete the old record, then insert a new one with the new values. so this may raise the delete trigger
>
>I think you misunderstood my message. I have a trigger in the SQL Server for Delete command. When a user wants to delete a records, this trigger is called (by SQL Server). The trigger updates several child tables. In my trigger code I still had the old table name that didn't need to be updated. Hence the error message. By commenting the "non-used" table name, the problem was resolved.


Ok. There was a lot of quirky stuff with column, record, udate and delete in this thread, possibly I missed something. Never mind.