Found the problem. Solved. Thanks, all. 
PrintError (boolean, inherited)

This attribute can be used to force errors to generate warnings (using
+ warn) in addition to returning error codes in the normal way. When s
+et ``on'', any method which results in an error occuring will cause t
+he DBI to effectively do a warn("$class $method failed: $DBI::errstr"
+) where $class is the driver class and $method is the name of the met
+hod which failed. E.g., 
  DBD::Oracle::db prepare failed: ... error text here ...
By default, DBI->connect sets PrintError ``on''.

If desired, the warnings can be caught and processed using a $SIG{__WA
+RN__} handler or modules like CGI::Carp and CGI::ErrorWrap.

[download]

In reply to PrintError (boolean, inherited) by nop
in thread Silencing the grumbling from DBD::ODBC by nop

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.