Digital certificate for Access 2002?

[StuartM]

Hi,

Is there any way of digitally signing an Access 2002 (aka XP) database? We
have a package that contains an MDE created in 2002 which also installs
runtime 2002. Everything has worked fine for all our customers until one came
along who had Access 2003 with its macro security settings. The customer have
their settings set at least to Medium (possibly High) and to block unsafe
expressions, which is causing all sorts of problems with command bars and the
AutoExec/AutoKeys macros in our app. AutoExec I can solve by using a startup
form, but command bars seem more troublesome.

It also appears that even though the Runtime for Access 2002 has been
installed - and the shortcut for our application explicitly points to its EXE
- that Access 2003 wants to get involved with its macro security settings.
I'm guessing this could be something to do with common DLLs etc. not being
overwritten, but wondered if anyone could confirm this.

Many thanks in advance,


Stuart

p.s. I've tried associating MDEs with the Runtime of 2002 but this doesn't
work either...

 

[Paul Overway]

Digital Certificates can be used in 2003, not in 2002. You'll need to have
the user disable their macro security, change their shortcut so that it
points to your runtime (if it is still there...they may have upgraded and
wiped it out), or sign your app with a digital certicate using 2003. The
first option is probably the best, because if you have an AutoKeys macro,
your app won't run properly even with a certificate. Plus there are other
issues with macro security.

 

[StuartM]

Thanks Paul,

Not the news I wanted to hear about 2002 not being able to be digitally
signed, but you've saved me a hell of a lot of searching!

I did make sure that the shortcut we install points to the 2002 runtime EXE
but 2003 still wants to come out and play. I should have explained that they
already have the full version of 2003 installed on their PCs, and they then
install our app with 2002 runtime at some point after. I haven't tested this
scenario fully so I can't say if it messes up any DLLs or 2003 critical files.

Cheers again,

Stuart