>The INSERT INTO command locks table header shortly to add new record. If another user already has table header locked than you'll get that error.
>
Ah... I should have checked SET REPROCESS help before I posted. I assumed that the default setting would have forced the app to try the lock indefinitely. I guess I should use AUTOMATIC or a finite number of attempts before letting ON ERROR take over.

Still curious, though, as to why the error reported that the cause was the call to a stored procedure for a table that had nothing to do with the INSERT.

Thanks for your quick reply Sergey.

Ed