It looks to me like you have one dot too many in OptionsDB..MyOpt .

Anyway, FWIW, here's a slightly shortened version of your script.

use strict;
use warnings;
use HTML::TableExtract;
use DBI;

my $dbh1 = DBI->connect('DBI:ODBC:OptionsDB', 'sa', '')
  or die "Couldn't connect to database: " . DBI->errstr;
my $sth1 = $dbh1->prepare(<<'EOSQL')
INSERT INTO OptionsDB.MyOpt
  (Security, Volume, Previous, TodayHigh, TodayLow, TodayClose, Change
+)
VALUES (?,?,?,?,?,?,?)
EOSQL
  or die "Couldn't prepare statement: " . $dbh1->errstr;

open CSEFILE, 'SCE.htm' or die "Failed to read SCE.htm\n";
my $response = do { local $/; <CSEFILE> };
close CSEFILE;

# Do you need the following s///'s transformations if you are going to
# have HTML::TableExtract parse $response ???
$response =~ s/.*Statistics//s;
$response =~ s/Volume Weighted Average.*//s;
$response =~ s/[\r\n]//gs;
$response =~ s/[ \t]+/ /gs;

my $te = HTML::TableExtract->new( headers =>
                                  qw( Security Volume Previous High
                                      Low Today's Change ) );
$te->parse( $response );
for my $ts ( $te->table_states ) {
  for my $row ( $ts->rows ) {
    print join( "\t", @$row ), "\n";
    $sth1->execute( @$row )
      or die "Couldn't execute statement: " . $sth1->errstr;
  }
}
[download]

Slightly shorter still...

for my $ts (HTML::TableExtract->new(headers=>qw(Security Volume Previo
+us High Low Today's Change))
  ->parse($response)->table_states ) {

  for my $row ( $ts->rows ) {
    print join("\t", @$row), "\n";
    $sth1->execute( @$row )
      or die "Couldn't execute statement: " . $sth1->errstr;
  }
}
[download]

Presuming that the s/// transformations may be unnecessary as tlm pointed out:

open CSEFILE, 'SCE.htm' or die "Failed to read SCE.htm\n";

for my $ts (HTML::TableExtract->new(headers => qw(Security Volume Prev
+ious High Low Today's Change))
  ->parse(do { local $/; <CSEFILE> })->table_states) {

  for my $row ( $ts->rows ) {
    print join("\t", @$row), "\n";
    $sth1->execute( @$row )
      or die "Couldn't execute statement: " . $sth1->errstr;
  }
}

close CSEFILE;
[download]

As to whether there are more efficent ways to do this, given the context you may be interested in the Finance modules.

The problem code is as follows:

    my $sql = q{select * from accountaction where action_date > ?};
    my $sth = $dbh->prepare($sql);
    $sth->execute('01-01-2006');
    $sth->finish;
[download]

    my $sql = q{select * from accountaction where action_date > '01-01
+-2006'};
    my $sth = $dbh->prepare($sql);
    $sth->execute();
    $sth->finish;
[download]

    my $sql = q{select * from accountaction where action_date > ?};
    my $sth = $dbh->prepare($sql);
    $sth->execute('2006-01-01');
    $sth->finish;
[download]

This response is being added to a somewhat old node because it is the only relevant one I found using Super Search, and I would like to save future searchers some trouble.

Huge thanks- you did in fact "save future searchers some trouble", big time!

I was getting this error too, and I didn't realize it was because I hadn't included the hyphens in the date. I'm so used to doing '20130325' in SQL Server, and it does accept that form in other contexts.

But for parameterized queries, apparently one needs the hyphens like "2013-03-25', because once I read your comment and put the hyphens in, problem solved.

(Yes I love replying to a post 7 years after it was written, just to say thanks to a guy who will probably never read this)

OptionsDB..MyOpt
OptionsDB is the Datebase
MyOpt is the table