You are indeed telling DBI that you will have one bind var with this line of SQL:

WHERE ((x Is Not Null) AND ([Today's Date]> ?))
[download]

But it seems that DBI (or the ODBC driver) doesn't like that line. First off, a field name of "Today's Date" is god-awful ... i don't use spaces or any special characters in my tables or my fields, regardless of whether or not it is valid to do so. It most definitely is not portable. Why not name that field today_date or such? Much easier to deal with.

My recommendation is to simplify your test, maybe something like:

my $dbh = (
   'connection string', 'user', 'pass',
   {RaiseError => 1},   # IMPORTANT!!!
);

my $sth = $dbh->prepare(q|
   select * from Referrals
   where [Today's Date] > ?
|);
$sth->execute($date);
[download]

And see what happens. If that doesn't reveal anything new, then how about simply:

my $sth = $dbh->prepare(q|
   select [Today's Date] from Referrals
|);
$sth->execute();
[download]

UPDATE:
I really am no DBI expert ... but this might just be a bug within DBI ... maybe DBI chokes on elaborate field names and or the square brackets when it tries to bind the vars. A cheap solution is to just interpolate $date instead your SQL string ... but only do this if you trust the contents of $date or really scrub it like skyknight suggested. (skyknight++)

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)