Unable to open db

[Powderfinger]

I am using Windows XP on the workstation. The "server" is running Windows
2000 professional. Access 2000. Everything has been working fine for years
except yesterday the XP machine did a windows update and now it can not open
the database which is on the Windows 2000 machine. It's giving me an error
message saying that there is a secuity risk.

Any suggestions besides upgrade the server to windows 2003 server?

There's got to be a workaround here

thanks

Jack

 

[Bill]

Exactly what does the error message say?

 

[BruceM]

It seems to me that the updates sometimes reset the macro security level to
high or medium. I tend to keep it at low, because when it is set to high
there are some things that just don't work and you never learn why. When it
is set to medium there is a message warning about the dangers of some
unnamed menace. I usually click through that warning, which has the effect
of setting the security to low. If I have reason to suspect a file I take
precautions before opening it. However, if there is a network administrator
it may be best to check before resetting anything.

 

[Powderfinger]

The Error message reads:

Microsoft Access can not 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
accessable network location.


Any suggestions?

 

[Powderfinger]

I have a correction. The Workstation is running Access 2002 under Windows
XP. I found a page on MS knowledgebase:
http://support.microsoft.com/kb/810582/el

But I'm still not able to fix the problem. I tried mapping a logical drive
so the db is S:\mydb.mdb instead of \\server\share\mydb.mdb and opening the
db using the s drive link, but I still get the same error message.

Jack

 

[Powderfinger]

I have fixed the problem but I appreciate the feedback.

I went into Internet Explorer\Tools\Internet Options\Security\Local
Intranet\Sites and check all those options.

Seems like this problem only occurs with Access 2002.

Jack