If you're deleting or modifying or re-creating any linked tables, that might require exclusive access. Access will automagically put you into exclusive mode if you do something like this.

Try closing out as soon as you've updated the DB.

-Cameron Wilhelm

On Thursday, July 17, 2003, at 02:21 PM, Will Howard wrote:


The problem might be overcome by instructing the other users to make
certain they do not open the database in "exclusive." I no longer have a
copy of Access 95 around, but I seem to recall that we had this problem
when the database was opened by another user who had "open exclusive"
checked in the dialog box where they selected the database to open. If
you go to the "Open" dialog box, you may see what I am talking about.

Will Howard

-----Original Message-----
From: J. Michael Roberts [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 12:32 PM
Subject: [PHP-DB] Access 95 ODBC Annoyance

I'll be the first to admit this is a rather backwards system and prone to be illogical, but it's what was handed to me and I can't do much about that.

I've got an ancient Access 95 database that I've linked to via another
A95 database which is queried via ODBC. It was done this way because I'm
not allowed to touch the first database due to the insane way they
replace the data each week. (i.e.: any of my tables would be gone, so I
need to keep 'my' data safe and link to 'their' data)

While under development, I was working with a copy of the database and
got everything to work fine. In order to "go live" with the current
data, I had to go into 'my' database and update the linked tables. When
this was done, my interface failed miserably and returned the following

Warning: SQL error: [Microsoft][ODBC Microsoft Access Driver] The
Microsoft Jet database engine cannot open the file 'T:\TS\Te_rdata.mdb'.
It is already opened exclusively by another user, or you need permission
to view its data., SQL state S1000 in SQLExecDirect in
C:\Apache2\htdocs\projecthours\deptjobs.php on line 44

Now it gets worse: I need to be able to access the data even if someone
has it open. Read-only access isn't a problem...because that's all this
particular interface does...but I just keep getting denied. Any ideas?

Suffering under a backwards system,

PS - Access is a hunk of crap...especially Access 95.

PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to