Cross network Access db connection problem

[Guest]

Hi

I wonder if you can help me. I've got an asp.net (version 1.1) intranet
application that connects across a network to an access backend db. The
backend db is on a directory where everyone (including the ASP.Net account)
has full access (not sure if that's the right way to go about things but it
works).

However my application now needs access to some information from another
network access db, which is on a directory where everyone (including the
ASP.Net account) has read & execute rights. When I try and open a connection
I get the "you can't do this because the db is already opened exclusively by
another user" message. I can't, and don't want to, change the directory
rights to the second db and it's in constant use so I can't kick people out.
Is there any way around this?

Thanks for your help in advance.

 

[Norman Yuan]

the user account must have write permission (because a *.ldb lock file needs
to be created whenever the *.mdb file is accessed). Also, ASPNET account is
local account to the computer where the ASP.NET application running. It does
not have access to other computers. Since its password is assigned randomly
by the computer, the ASP.NET account on the other computer would have a
different password. So, very likely, ASPNET account cannot access anything
on the network. If you need to access something on the network, consider to
impersonate the ASP.NET running account to a domain account that have proper
permission to the network resources.

 

[Paul Clement]

¤ Hi
¤
¤ I wonder if you can help me. I've got an asp.net (version 1.1) intranet
¤ application that connects across a network to an access backend db. The
¤ backend db is on a directory where everyone (including the ASP.Net account)
¤ has full access (not sure if that's the right way to go about things but it
¤ works).
¤
¤ However my application now needs access to some information from another
¤ network access db, which is on a directory where everyone (including the
¤ ASP.Net account) has read & execute rights. When I try and open a connection
¤ I get the "you can't do this because the db is already opened exclusively by
¤ another user" message. I can't, and don't want to, change the directory
¤ rights to the second db and it's in constant use so I can't kick people out.
¤ Is there any way around this?
¤
¤ Thanks for your help in advance.

Without sufficient permissions to the resource you would have to open the database for read-only
access in order to suppress creation of the corresponding .LDB file.


Paul
~~~~
Microsoft MVP (Visual Basic)