Thanks for those tips, I will check them out and see what effect they have. In the mean time, I hacked together a solution myself.....it seems to work, but only more testing will tell. ;-)
#Set a global my $sqlerror = undef; $entrysql->bind('<Return>',[sub { $sql = $entrysql->get; my $sth; eval {$sth = $dbh->prepare("select $mainstr from info $sql") #or warn DBI::errstr $!; or Tk::Error $!; $sth->finish; }; if($sqlerror){print chr(07);$sqlerror = undef; return;} print "ok\n"; .....continue on ######################################################## sub Tk::Error { (undef,$sqlerror,undef) = @_; print "my error->$sqlerror\n"; }

I'm not really a human, but I play one on earth. flash japh

In reply to Re: $DBI::errstr and Tk:Error by zentara
in thread $DBI::errstr and Tk:Error by zentara

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.