In addition to what repson said, you may want switch on RaiseError: 
my ($dbh) = DBI->connect("DBI:ODBC:messagestore", "user", "password", 
+{RaiseError => 1});

[download]
This allows for a more extensive amount of information when dying than what you have now.

Furthermore, 
my ($message_id) = $data[1];
my ($message_date) = $data[2];
my ($message_time) = $data[3];
my ($message_sender_name) = $data[4];
my ($message_to_name) = $data[5];
my ($department_id) = $data[6];

[download]
is better written as: 
my (undef, $message_id, $message_date, $message_time, $message_sender_
+name, $message_to_name, $department_id) = @data;

[download]
At least, that's my opinion :-)

[ ar0n ]

In reply to (ar0n) Re: More DBI Problems!!! by ar0n
in thread More DBI Problems!!! by grax

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.