I discovered the problem at had was in the network permissions set on 
the file (?) that was denying Apache to access it properly and the error 
code returned was the best thing the system could come up with.

I changed my Apached service to 'run as' and authorized user (me) and it 
happily viewed the data.


J. Michael Roberts wrote:

>I'll be the first to admit this is a rather backwards system and prone to
>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 message:
>Warning: SQL error: [Microsoft][ODBC Microsoft Access Driver] The Microsoft
>Jet database engine cannot open the file 'T:\TS\Te_rdata.mdb'. It is
>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.

Reply via email to