The above answers are all very much right in identifying the problem as your usage of place-holders. One other minor point about your program design that might help you: you pass param('grp_name') to DBI without checking its validity or existence. If that parameter is undefined, you will get an error (actually, the same one you got here but with the numbers reversed. You might want to consider doing something as simple as this:

my $grp_name = param('grp_name');
if (exists($grp_name)) {
     $sth->execute($grp_name);
     }

[download]
Or you could get more complicated and check the validity of param('grp_name') with an appropriate reg-ex. In short: it's usually a good idea to validate your parameters before passing them to the database.
Hope it helps,
-Tats
Update: Fixed grammar error

In reply to Re: Need help with DBI bind value error by Itatsumaki
in thread Need help with DBI bind value error by miller

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.