Hi,

terce is correct. Also you should close the connection once you are done with it:

$data->Close();

You may also want to do some error checking:
if ($data->Sql($SQL)) { print "The SQL failed.\nError:" .Error(); } else { print "Sql inserted\n" }

The complete code with the fix pointed out by terce and the above error checking is:

use strict; use Win32::ODBC; my $data = new Win32::ODBC("DSN=SQLServer") or die "Could not open bec ++ause of [$!]"; my $SQL = "SELECT itemNbr, Store_Num FROM sales"; if ($data->Sql($SQL)) { print "The SQL failed.\nError:" .Error(); } else { print "Sql inserted\n" } $data->Close();

N.B. The above code is untested but I'm pretty sure that it works.
If you are unsure of things always read the documentation.
Hope this helps

Martin

In reply to Re: can't call method 'Sql' on an undefined value by marto
in thread can't call method 'Sql' on an undefined value by Anonymous Monk

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.