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

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!!!

Replies are listed 'Best First'.
Re: Re: Re: Perl to MS Access with DBI:ODBC on Unix
by TStanley (Canon) on Dec 28, 2000 at 23:26 UTC
    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.