Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

Re: Perl to MS Access with DBI:ODBC on Unix

by coreolyn (Parson)
on Dec 28, 2000 at 20:58 UTC ( [id://48638]=note: print w/replies, xml ) Need Help??


in reply to Perl to MS Access with DBI:ODBC on Unix

It sounds like your not defining the ODBC data source on the NT side. The dsn="dbi:ODBC:$odbcDataSourceName" as defined in the NT ODBC manager.

I should note however that the only way I was able to get it working was by resorting to the DBI::Proxy on the NT box and having the unix box talk to the proxy1.

coreolyn


1 See pg 179 of The Cheetah
  • Comment on Re: Perl to MS Access with DBI:ODBC on Unix

Replies are listed 'Best First'.
Re: Re: Perl to MS Access with DBI:ODBC on Unix
by PsychoSpunk (Hermit) on Dec 28, 2000 at 22:39 UTC
    As a followup to this, with standard disclaimer that I have not used OpenLink for this exact connection, I am going to run under the following assumption:

    You are using the OpenLink Request Broker on NT.

    If this is the case, I'm going to guess that you simply either make a connection to the Access database engine using the OpenLink software and specify the database in your DBI connect string.

    $dbh = DBI->connect('dbi:ODBC:server=$server;database=$mdbfile', $user, $pass, { RaiseError => 1});

    Thus, you're making your connection to Access and giving it the database file you wish to use. On the NT side, you may or may not need to provide a database specification in the OpenLink DSN.

    This is just a hazarded guess, but it would seem to be consistent with the DBI API, and from what I've seen of OpenLink (I use it for MS SQL 7 connections), it should be adequate, although I've only used DSNs with defined database connections. However, since each database engine has its own set of quirks, this may be the right way for Access.

    ALL HAIL BRAK!!!

      Just out of curiosity, do you have any problems with memory leaks?
      My company's software and Openlink aren't playing nice, as there is a
      very LARGE memory leak being caused by Openlink (We confirmed that
      our software wasn't at fault, and Openlink said there was a bug with the
      drivers (Version 3.2). We also checked the 4.0 drivers, and still
      have the same problem.

      TStanley


      Update:We looked a little bit further into the problem and realized
      that our software did have the memory leak. Since Openlink
      doesn't play nice with us, we are now using Merant's DataDirect driver.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://48638]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others sharing their wisdom with the Monastery: (5)
As of 2024-03-29 15:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found