I have done this kind of thing, and I check the value of $DBI::errstr to see if I could connect to the Database. After I do an insert I turn around and do a select and check the return code to make sure the records were added.
I am sure there are other and better ways out there through. Thanks, John Herbold IS Specialist/DBA -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 05, 2002 5:39 AM To: [EMAIL PROTECTED] Subject: Error handling with DBI Hi, I want to write a program that acesses two databases, fetching data from one, writing to the other. The core code works fine now, but i have several thoughts left: The program shall run as WinNT Service, running every 10 minutes or so. So the program may not "die" when it can't connect, but just wait until the next run. I also need some verification of the data being written to the second DB before deleting it from the first, would a construction like this work? if ($mssth->execute) { <no error>; } else { <error to log>; } regards, Lars
