in reply to Can't locate DBD/ODBC.pm in @INC

  1. Initially, as has been said: use your operating system to confirm that the file does exist in the directories specified in @INC
  2. write more by way of explanation of what you've done subsequent to downloading the module, otherwise a lot of well meaning monks'll be telling you stuff you may already know. Which is a waste of everyone's time :)

--
Brother Frankus.

Replies are listed 'Best First'.
Re: Re: Can't locate DBD/ODBC.pm in @INC
by Fian (Novice) on Mar 15, 2001 at 20:25 UTC
    OK.
    ODBC is in the directories specified in @INC.
    PPM did'nt download and install DBI so I downloaded DBI.zip from www.activestate.com After unzipping it I read the readme which said:
    "To install this ActiveState PPM package, run the following command in the current directory: ppm install DBI.ppd
    This I did and it replied with
    writing c:\BIN\perl\site\lib\auto\DBI\.packlist
    And that was it. I get the error that I wrote about before when I try to run the script.


    Tell you what. Could someone direct me to a site that offers tutorials on how to use Perl to access a database. Preferably an MS Access database

    Thank you..

      Tell you what. I'll actually address the problem you're describing, rather than blowing you off. and as for DBI tutorials, you're soaking in them!

      You're only getting half of what you need. DBI is the "Database Interface" half. The part I think you're missing (based on the error messages you report, and the process you've described) is the DBD -- "Database Driver". Look on PPM or CPAN for DBI::ODBC.

      See, much like ODBC, DBI only describes a common set of methods for accessing data stores. You need download the drivers which actually implement those methods. As always, CPAN has your hookup
      Once you've got that installed, you can use

      $dbh = DBI->connect('dbi:ODBC:DSN', 'user', 'password') || die ("Can't + connect to database : ",$DBI::errstr);
      to connect to your database. You may need to alter the dbi:ODBC:DSN portion depending on how your database is set up.
      Also note the $DBI::errstr; when debugging database problems, this variable is your best friend -- it'll report database errors, not perl errors, like $! and $@ do.
      once the connection's made and the $dbh is live, you can start preparing SQL :
      $sql = $dbh->prepare ("SELECT field FROM table") or die ("Unable t +o prepare statement: ",$DBI::errstr);
      Again, notice the die. If this statement dies, there's typically a problem with the statement's syntax, or the database handle ($dbh) is undefined.

      This is where the fun happens :

      $sql->execute()or die ("Unable to execute get_servertime : ",$DBI: +:errstr);
      This will set the SQL gnomes scurrying, and stores the result of the statement in $sql.

      Now that the results are in, how to read them? It depends. There's several methods of doing so, and each one is detailed in the documentation. My most often used one is

      @l_row = $sql->fetchrow_array;
      , but there's other methods of doing so. There's a nice hash method which'll store the field names as the hash keys, so you can manipulate$row{fieldname} if that's clearer than working with array elements.

      When everything's done and said,

      $dbh->disconnect
      to close the database. For further information, see Programming the Perl DBI, and of course, DBI's own POD, which has a synopsis of how to connect and read to a database.

      OK?