500 internal server error sounds awfully like an HTTP error and not an ODBC one. What happens when you run sql2 from a command prompt within a simple perl script? What error is raised/output? When we see what actual error you are getting we might be able to help.

With sql 6/7/8 it would probably be useful to know the schema and possibly a DBD::ODBC trace which you can get by setting (and exporting if UNIX) DBI_TRACE to "15=x.log" then the trace goes to x.log. But you need to simplify further to a straight forward perl script run from the command line. BTW, you did run DBD::ODBC's test suite to MS Access didn't you?

What versions of DBI and DBD::ODBC are you using? and what platform are you running this on.

In reply to Re^5: Fetching data from Access using DBI by mje
in thread Fetching data from Access using DBI by hacheb

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.