I don't have the docs in front of me, but read the DBI docs. Basically what you need to do is turn attributes 'raiserror' and 'printerror' off.

Personally, however, I would never do that. Why not test the tables, see if they are there and then remove them. You can get the errors into your programme, but why do you have to do anything with them? If they are about things like attempt to write a duplicate record or such, you can sensibly choose what to ignore and what to take seriously.

A missing table is not an error to necessarilly die for. But it is that sort of behaviour in PHP which keeps many Perl programmers from using it. My in-house PHP hacker searched for several hours the other day to find out why his script wouldn't write teh data it was supposed to... he wasn't trapping any errors and the table was not present... his table creation code had not worked but he did not realise it.

jdtoronto