I had this exact problem and it took me days of beating my head against the
wall to find the solution.  First, you do want to make sure that the Access
security permissions are correct on the database.  For example, "Admin"
typically needs to be the owner; it can sometimes get corrupted, causing a
problem.  Secondly, you need to make sure that the IIS user account has the
appropriate NT permissions to the database.  I have found that write access
is required for it to work.  Thirdly, and most likely your problem, is a bug
in IIS.  Check out Microsoft TechNet article Q189408 (FIX: ASP Fails to
Access Network Files Under IIS 4.0 and IIS 5.0).

~~~~~~~~~~~~~~~~~~~
Bill Mayo
Network Administrator
Pitt County MIS


> -----Original Message-----
> From: Daniel Furse [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, February 28, 2001 9:52 AM
> To:   PHP Windows List (E-mail)
> Subject:      Connecting to remote databases
> 
> Hi everyone,
> 
> I'm trying to connect an Access database that is not on the same server as
> the web server. All the servers are Windows NT 4, the web server is IIS4,
> and I'm using PHP4. Whenever I try to query the database, it returns:
> 
>       Warning: SQL error: [Microsoft][ODBC Microsoft Access 97 Driver] The
> Microsoft Jet database        engine cannot open the file 'SIDSC.MDB'. It
> is
> already opened exclusively by another user, or        you need permission
> to view
> its data., SQL state S1000 inSQLExecDirect 
> 
> I've checked that the database is not opened by anyone else. I've also
> tried
> creating a new database on the web server and creating links to the tables
> in Access, but I still get the same error. The remote database has read
> permissions for the 'Everyone' group, so does the entire directory path,
> and
> the share.
> 
> Can anyone help?
> 
> Many thanks,
> 
> Dan

-- 
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to