Stan Brown [[EMAIL PROTECTED]] wrote:
> I have a fair sized perTK script that makes heavy use of DBI. As I put the
> final touches on it before releasing it for production use, I'm trying to
> cleanup the error handling a bit.
>
> What I have at the moment is that (somehow automagicly) I get a warning box
> to pop up with the full text of what I think is the DBI error string. While
> this is nice, I need to clean these messages up a bit for easier user
> understandibilty.
>
> As I set off down this road this morning, the first thinh I decided to do
> was change the seting of PrintError at various places in my script where I
> pretty much "expect" errors (duplicate rwo insert failures etc._
>
> So I put in:
>
> $sth-<(PrintError) = 0;
What I see on p.92 is this:
$h->{PrintError} = 1;
--
Hardy Merrill
Mission Critical Linux, Inc.
http://www.missioncriticallinux.com
>
> as shwon on page 92 of the O'Rielly book. However this gives me an arror
> about barewords not being allowed there.
>
> What am I doing wrong? and how can I aquire the current state of this
> variable, so that I can save it, and restore it to it's original value,
> after I make a local change to it?
>
>
> --
> Stan Brown [EMAIL PROTECTED] 843-745-3154
> Charleston SC.
> --
> Windows 98: n.
> useless extension to a minor patch release for 32-bit extensions and
> a graphical shell for a 16-bit patch to an 8-bit operating system
> originally coded for a 4-bit microprocessor, written by a 2-bit
> company that can't stand for 1 bit of competition.
> -
> (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
