The error message is what is created by the driver, that is, the Access client libraries - there isn't much that Perl can do.

Most likely it will help you to either increase the tracing level of DBI via

DBI->trace(99);

Often it also helps to simply print out the SQL before executing it. The SQL in question is in line 1 of some file you didn't who. 1 seems a weird line number, but that's what you tell us.

You are not interpolating variables into your SQL, are you? You should read up on placeholders and use those. That eliminates most types of syntax errors with your SQL.


In reply to Re: DBI SQL error messages by Corion
in thread DBI SQL error messages by rjberry

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.