I tried subscribing but the list server does not appear to be working.
Hmmm.. well maybe I'm mistaken. I just tried again and it sent me a
confirmation this time.
I figured out my problem: Microsoft Access does not use the traditional
architecture where clients use pipes or sockets to connect to a process on a
(possibly) remote machine. Instead it creates a temporary file with the
extension of ldb.
If users from two different accounts have access to the database file
because the administrator granted them access, the second user will still
have a problem because he won't be able to access the temporary ldb file
created by the first user.
My solution is to have everyone use the same account. This works because in
my situation, one user is a web server and the other user is a batch job
that runs every couple of hours.
From: Timothy Johnson [mailto: XXXX@XXXXX.COM ]
Sent: Thursday, October 20, 2005 3:54 PM
To: Siegfried Heintze; XXXX@XXXXX.COM
Subject: RE: Simultaneous access: Perl (DBD::ODBC) and C# (ODBC)
I have two suggestions:
One is to go to http://www.yqcomputer.com/
and sign up for the dbi-users
Two is just a thought, but have you tried using DBD::ADO instead of
From: Siegfried Heintze [mailto: XXXX@XXXXX.COM ]
Sent: Thursday, October 20, 2005 2:15 PM
Subject: Simultaneous access: Perl (DBD::ODBC) and C# (ODBC)
<snip>DBD-ADO interaction issue</snip>