Shared drive won't let Access XP open a file.

[Guest]

I have a simple and small database developed in A2K and stored on a shared network drive (S drive); My problem is that when I attempt to open the db using AXP, I get an error that tells me the drive is not part of my local intranet or part of my trusted sites, and that Access won't open it.

There is NO security on the db, not even a simply password.

When I move the db to the local drive it works perfectly, move it back to ANY network drive and it can't be opened.

Create a brand new database and attempt to import the objects and I can't access the db on the network.

Create a brand new database in AXP and save it to a network drive and it saves fine. Close and relaunch AXP and attempt to open the just created/saved db and it doesn't want to play with the network.

This has stumped our network administrator as well; He even gone so far as giving everyone full administrator rights to the shared drive and still AXP doesn't want to talk to the network. All the other Office XP apps work fine with the shared drives, Access is the only pouty app.

We've read everything in AXP Help on Security Zones and have even specifically listed the network drive and the full path to the db file and still AXP doesn't want to play nice.

It seems like another one of these Microsoft paranoia issue where one application (Access XP) won't trust the settings of another (Windows XP).

At present we are working around this issue by using the db on a single local hard drive, but that will last for only a couple of days, then we have to move on with the reality that this needs to be on a shared drive.

Does anyone understand Security Zones &/or why we can't open the db on network drives but only on the local drives.

 

[Roger Abell]

AFAIK you are on the right track, the behavior you see is
due the to Security Zones settings. Perhaps you could ask
over in an IE newsgroup (?) and someone might know.
I have seen a number of people with local access to exe
files, but not mdb yet (until now). Most seem to have been
able to resolve things by adding the local machines to the
intranet or trusted sites zones and then tweaking with the
IE security zones there.
Sound like you are now saying, been there done that.
Have you the same issue if you map the share and then
launch Access by clicking on the mdb in an Explorer drive
lettered path ??

--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA

I have a simple and small database developed in A2K and stored on a shared

network drive (S drive); My problem is that when I attempt to open the db
using AXP, I get an error that tells me the drive is not part of my local
intranet or part of my trusted sites, and that Access won't open it.

There is NO security on the db, not even a simply password.

When I move the db to the local drive it works perfectly, move it back to

ANY network drive and it can't be opened.

Create a brand new database and attempt to import the objects and I can't access the db on the network.

Create a brand new database in AXP and save it to a network drive and it

saves fine. Close and relaunch AXP and attempt to open the just
created/saved db and it doesn't want to play with the network.

This has stumped our network administrator as well; He even gone so far as

giving everyone full administrator rights to the shared drive and still AXP
doesn't want to talk to the network. All the other Office XP apps work fine
with the shared drives, Access is the only pouty app.

We've read everything in AXP Help on Security Zones and have even

specifically listed the network drive and the full path to the db file and
still AXP doesn't want to play nice.

It seems like another one of these Microsoft paranoia issue where one

application (Access XP) won't trust the settings of another (Windows XP).

At present we are working around this issue by using the db on a single

local hard drive, but that will last for only a couple of days, then we have
to move on with the reality that this needs to be on a shared drive.

Does anyone understand Security Zones &/or why we can't open the db on

network drives but only on the local drives.