On Wed, 4 Dec 2002 16:33:34 +0100 [EMAIL PROTECTED] wrote: > ok, here wo go. What I already found again is, if I take out the 'print > "$DBI::errstr\n";' statements the error disappears again... Maybe I only > may > access $DBI::errstr if there really is an error?
You are printing $DBI::errstr even when no statement has been executed to set it. Try protecting the print() with $DBI::err: print "$DBI::errstr" if $DBI::err; It appears that when you use $DBI::errstr before any statement has set errstr (even to undef), bad things happen. Perl shouldn't blow up in that case, but until the problem is tracked down, "Don't do that". -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age.
