Provider for ODBC Drivers (0x80004005) error with linked tables

I have an Access 2000 database with tables linked from multiple Access
databases. The set runs fine on my web service. That is, with all the
database files present on the remote server the code on the remote
server behaves.

What I can't do is test locally. I've set up a virtual drive to a local
hard drive that mimics the path on the internet server. The main
database links to the sub databases using this virtual path. I can open
and query all the tables when I'm in the database.

When I try to use IIS on my development machine, which has the files
stored in INETPUB, I get an error message that the 'path' is not a
valid path. This doesn't make any sense. I've reached that conclusion
that this is happening because of some Microsoft security thing, but
I've not been able to determine what it is and how to disable it.

Any suggetions gratefull accepted.

Re: Provider for ODBC Drivers (0x80004005) error with linked tables

http://aspfaq.com/show.asp?id=3D2009

http://aspfaq.com/show.asp?id=3D2413

--=20
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

wrote in message =
news:1109616331.620619.225910@l41g2000cwc.googlegroups.com.. .
> I have an Access 2000 database with tables linked from multiple Access
> databases. The set runs fine on my web service. That is, with all the
> database files present on the remote server the code on the remote
> server behaves.
>=20
> What I can't do is test locally. I've set up a virtual drive to a =
local
> hard drive that mimics the path on the internet server. The main
> database links to the sub databases using this virtual path. I can =
open
> and query all the tables when I'm in the database.
>=20
> When I try to use IIS on my development machine, which has the files
> stored in INETPUB, I get an error message that the 'path' is not a
> valid path. This doesn't make any sense. I've reached that conclusion
> that this is happening because of some Microsoft security thing, but
> I've not been able to determine what it is and how to disable it.
>=20
> Any suggetions gratefull accepted.
>=20

Re: Provider for ODBC Drivers (0x80004005) error with linked tables

Good information, but it doesn't seem related. The main database is
fine as is. The application, as I mentioned, works fine on the web.

I have a local device for development and testing. When I attempt to
run the application locally it shows me the path for the linked table
and says it's not valid, which is a little weird, since it's local to
the machine running IIS.

Thanks for the links.