I recommended you take a look at DBD::ADO, it does all that Win32::OLE ADO stuff for you in familiar DBI style ... so you don't have to suffer the maze of OLE :)
#!/usr/bin/perl -- use strict; use warnings; use Data::Dump qw/ dd pp /; use DBI(); Main( @ARGV ); exit( 0 ); sub Main { my $att = {qw/RaiseError 1/}; my $user = my $pass = undef; my $dbh = DBI->connect("dbi:ADO:$dsn", $usr, $pwd, $att ) ; $dbh->trace(3); my $sth = $dbh->prepare( $mssql_select ); dd( $sth->execute ); dd( $sth->fetchall_arrayref ); }

See also Tutorials->Database Programming->DBI recipes


In reply to Re^3: Perl OLE32 MSSQL SELECT dateadd function results in “Cursor type changed” error by Anonymous Monk
in thread Perl OLE32 MSSQL SELECT dateadd function results in “Cursor type changed” error by newbieperlperson

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.