I have an access database that is on server x iis running on server y. One of my web pages is accessing data from an access database. If someone has access to the access database, say that the end user on our network has failed web pages ... is already opened exclusively by another user error message.
I created a local access database and used linked tables to access the tables this way. Even so far, I am getting a completely different user error that is already open. If I go through Windows Explorer and browse the x server and open the database, I can no problem. So my question is how to simulate the same type of database connection without error, is it a question of allowing access to the access database or something in my connection string that will allow me to access the database.
Since it throws an error during my connection.open command, I believe that this is due either to permission or to something additional that I need to add to the connection string. I gave full control over IIS AppPool \ in the local directory where my local access database instance is located, but it doesn't seem to matter.
My connection string looks like this:
Private Shared connSheriff As New OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\serverx\directory\Access\MyDatabase.mdb;Jet OLEDB:Database Password=property;")
source
share