I was about to post and say that while DBD::ODBC is preferable from a programming standpoint, it has the inconvenience that it requires you to setup an explicit DSN in your ODBC Data Sources area. But I would have been wrong! To quote from the POD:
Example (using MS Access): my $DSN = 'driver=Microsoft Access Driver (*.mdb);dbq=\\\\cheese\\g$\\perltest.mdb'; my $dbh = DBI->connect("dbi:ODBC:$DSN", '','') or die "$DBI::errstr\n";
Obviously, the usual caveats about using Access programmatically apply (it's a single user database so watch out for threading and locking issues, it should be located preferably on the same machine as the application or at least within the same LAN, etc). I had the experience of trying to programmatically fetch data from .MDB files on machines halfway across a large corporate Intranet. It wasn't pretty.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|