This is an issue with DBI placeholders and not strict. Your problem is that you're calling execute() with a placholder value where your SQL doesn't have a placeholder in it. Your code should probably look more like this (formatting added for my own benefit :) 
my $sqlcount = 'SELECT COUNT(*) FROM grp_def WHERE grp_name = ?';

my $sth = $dbh->prepare($sqlcount)
  or die "Cannot prepare: " . $dbh->errstr();
$sth->execute($grp_name)
  or die "Cannot execute: " . $sth->errstr();

my $occurences = $sth->fetchrow_arrayref->[0];

print "result: $occurences\n";

[download]
There I've moved $grp_name out of the SQL and moved into the execute() and replaced it with a placeholder. For more info on placeholders see the Placeholders and Bind Values section of the DBI docs.
HTH

_________
broquaint

In reply to Re: Need help with DBI bind value error by broquaint
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.