Just a note, the database will only report the error if it gets the SQL command. In this case, the ODBC driver never passes it along (what's the point if it fails the checks before going to be executed at the database?). And also, regardless of where the error occurs, DBI has a property to store all errors. $dbh->errstr or $DBI::errstr always holds the last error for the dbh or the last error that occurred.

Most developers will bypass the need to physically print this by setting RaiseError => 1 when creating the dbh. It may be that MS SQL 7.0 was logging the error and Ovid didn't list that info.

My own question to Ovid is why you chose to use ODBC. I'm not knocking its use, since I did the same thing, but I was curious if you tried FreeTDS, and if so, what errors came up.

I had troubles with it and MS SQL 7.0 although people say it's possible, I've not seen it in my own experience, and no one has come up with any documentation that explicitly lines out what tweaks were necessary. It'd be nice if a user was so inclined to show us the light.

Thanks if anyone takes this to task. ALL HAIL BRAK!!!

In reply to RE: RE: (Ovid) Re: DBI Problem Solved by PsychoSpunk
in thread DBI Problem? by Ovid

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.