in message:
Jeff,
Thanks for your information.
However, I still do not understand why Microsoft creates such issue to all
users of Access 2003. At least, there is no good reason. In addition, if
the Windows xp has been installed all upgrades, the Microsoft Jet 4.0
Service Pack 8 should be installed as well. I cannot prove it correct since
the warning keeps on displaying and the turning on Sandbox Mode does not
appear so I cannot turn it to sandbox mode to avoid security warning. This
will discourage the users to upgrade it. Microsoft must address it!!
Hi Ray,
Well I certainly do not presume to know all of Microsoft's reasons for the
security changes, but this is definitely a sore spot with Access developers
for sure. Trust me. Do some Google searches on the subject and you will
not doubt find some strong opinions on this matter.
Microsoft is very much concerned about security, which is a good thing.
Since Access uses VBA there are many things that can damage a system
through some simple VBA commands. Is it a security risk? I would have
to say "Yes." The big question is, "How much of a risk?" That is the
debatable part. Personally I think people that enjoy doing damage to other
people's systems have much better tools at their disposal than Access/Jet
databases.
You must also remember something about the Jet SP 4.0 issue. When
Access 2003 was first released in October of 2003, Microsoft did not
have the SP 4.0 ready in time for the release media so it had to be
downloaded from Microsoft's site. Since that release, there has been at
least one security update to the Jet database engine. Not everyone does
a good job of keeping their systems up to date with the latest Windows/
Office Updates as well which creates additional problems.
Here is some good information I saved from MVP Allen Browne on this:
"The recommended solution is for your company to shell out money buying a
digital certificate to let you open your own database, and of course you
have to keep buying the certificate every year. If you are an individual you
cannot get a certificate. If you make even minor changes to your database
(such as changing an action query), you must go through the process of
signing it again, and there several related problems with constantly
changing a signed database.
The not-recommended solution is to set the Macro Security to Low, so Access
2003 behaves like Access should and like the previous versions do that do
not have this problem. (You can also avoid some of the dialogs by
sacrificing functionality.)"
And a comment by MVP John Viescas:
"...The last one is a real pain. You need to install JET SP8
from Windows Update (not included with Office 2003) to get
this to work properly. I suspect most folks will change
their macro security setting to Low to avoid the security
prompts."
I'm sure Microsoft has taken some heat for this issue. You can always
send along your own comments as well:
http://support.microsoft.com/contactus/?WS=Wish