Just my opinion, but I don't think this is good advice. For
one, it creates extra administration on the system, by
forcing the user/programmer /sysadmin/webadmin to create an
ODBC DSN setting for every new setup. For two, DBI and ODBC
both support dynamic DSNs, so why not use them?
If
, 2005 6:45 PM
To: Moreno, Javier
Cc: dbi-users@perl.org
Subject: Re: Accessing MS Access through the DBI ODBC
Hi Javier,
I am trying to access an MS Access database via perl DBI and I am unable to.
I checked the security and there is only one 'Admin' user with no password
and I use
, Javier
Cc: dbi-users@perl.org
Subject: Re: Accessing MS Access through the DBI ODBC
Hi Javier,
I am trying to access an MS Access database via perl DBI and I am unable to.
I checked the security and there is only one 'Admin' user with no password
and I use that in my connection string
From: Kevin Carothers [EMAIL PROTECTED]
Date: 2005/03/30 Wed PM 06:44:48 CST
1. Create an ODBC connection via %SystemRoot%\system32\odbcad32.exe
Call the database connect name ODBCName
2. In your Perl code add:
[---]
use DBI;
[---]
$dbh =
Hi Javier,
[---]
And on the log I get:
[Thu Mar 31 07:12:56 2005] [error] [client 151.110.117.153] DBI
connect('CLUCTR','',...) failed: [Microsoft][ODBC Microsoft Access Driver]
The Microsoft Jet database engine cannot open the file '(unknown)'. It is
already opened exclusively by
Hi Javier,
I am trying to access an MS Access database via perl DBI and I am unable to.
I checked the security and there is only one 'Admin' user with no password
and I use that in my connection string. However, I cannot connect. Please
help.
1. Create an ODBC connection via
