Unable to open Access on Local Area Network

[MikeWaring]

We have recently created a database on one PC and need to access it on that and one other PC. When we try to open the db from the other PC, Access attempts to open but then we get a snap window that says:



"MS Access Cannot open this file
This file is located outside your intranet or on an untrusted site
MS Access will not open the file due to potential security problems
To Open the file, copy it to your machine or an accessible network location"

We've added Access.exe and even this particular database to the allowed programs on both pc's firewalls but no luck. We've also put the db in a separate folder on the host pc's C Drive and shared the folder and C drive.
We've even tried mapping the db using the "Map Network Drive" process but still the same problem.

We can actually see the db icon image on the other pc and can open and work on any other type of file across the same network (either way between the pcs), so it doesn't appear to be a network or firewall issue.

I can only presume this is a problem with Access itself, but I have no idea how to overcome it.

As this db is used all the time, we can't have 2 separate versions as it is impossible to keep them both synchronised.

Both PCs are running identical OS (XP Pro SP3) and MS Office XP.
Access version is 2002 SP3
AV / Firewall is Symantec Corporate Firewall v 7.1.2.1201.
MS Windows Firewall is disabled.

Could someone please help as I'm completely stumped on where to go next.
Thanks in advance
Mike

[pkstormy]

The error you stated is very similar to the error I was getting. To solve my problem (even though it seems weird), I had to go into Internet Explorer (not Windows Explorer), go to Tools, Internet Options, then Security, and then Local Intranet. I then clicked the Sites button, then Advanced button and added our F:\ drive to the zone (you could also try lowering the security bar.)

This resolved my problem. I'm not sure if this will resolve your issue but it seems likely that's the problem given the description of your error. It's worth a shot.

Let me know if this works.