Ah, the joy of interpolation variables into SQL. If one of your variables contains a quote, the resulting string is likely to not be a valid SQL command, and hence, your database will barf.

The solution is to use placeholders. Like this: 

# Assume 'RaiseError' is set, and 'AutoCommit' is off.
eval {
    my $sth = $db -> prepare (<<"    --")
        INSERT INTO $Table[$II]
        VALUES (?, ?, ?, ?);
    --
    $sth -> execute ($ID, $Itemname, $Firstbid, $Endingprice);
};
if ($@) {
    $dbh -> rollback;
    die $@;
}
else {
    $dbh -> commit;
}

[download]

This assumes that @Table contains valid table names.

Abigail

In reply to Re: MS Access/ODBC error: why?? by Abigail-II
in thread MS Access/ODBC error: why?? by luoina

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.