Security warning, digital signing

[Guest]

I have a runtime application that is experiencing difficulty with security
warnings. I have a customer who installed my application and it ran without
problems. She wanted a couple of changes, which I made to the front end.
The backend was not changed. I emailed the new frontend MDE file. She
copied over the exsisting file, but now gets this security warning when she
opens the file.

Business Manager cannot open C:\Program Files\MQBMver1.1.mde due to security
restrictions. Security settings restrict access to the file because it is not
digitally signed.

She does have Access 2000 (I think) installed on her computer.

Does anyone have any ideas on why this is happening and what to do.

Thanks,
Mary

 

[MikeC]

Mary,

It sounds very much like your customer has Access 2003
installed. One of my customer's recently reported a
problem that sounds very similar to the one you
describe...right after she upgraded to Access 2003. Just
to be sure, I highly recommend that you have your customer
verify the Access version she is running.

If she has Access 2003, then you will need to learn about
Access' new security features. The below link to
Microsoft's Access Security Warning FAQ page may prove
useful.

http://office.microsoft.com/en-
us/assistance/HA011225981033.aspx#010

There are a number of questions and answers on the page as
well as links to related information. I think the more
useful information is down around item #22.

-----Original Message-----
I have a runtime application that is experiencing difficulty with security
warnings. I have a customer who installed my application and it ran without
problems. She wanted a couple of changes, which I made to the front end.
The backend was not changed. I emailed the new frontend MDE file. She
copied over the exsisting file, but now gets this security warning when she
opens the file.

Business Manager cannot open C:\Program

Files\MQBMver1.1.mde due to security

 

[Brendan Reynolds]

That's the message you get in Access 2003 (not Access 2000 or Access 2002)
when "macro" security is set to High and the VBA project is not digitally
signed. If you have a code signing certificate and are using Access 2003,
you can digitally sign the VBA project, otherwise the user or her
administrator will have to change "macro" security in Access 2003 to Medium.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

 

[Brendan Reynolds]

The customer may have Access 2000, but you're distributing an Access 2003
runtime, right? The customer can't change the setting in Access 2000 because
it didn't exist in Access 2000, and even if it did, it wouldn't help because
your application is not running under Access 2000 but under the Access 2003
runtime. What I do find puzzling though is how the "macro" security setting
got set to High for Access 2003, I'm fairly sure it defaults to Medium.

Unless you're using new Access 2003 functionality that wasn't supported in
Access 2000, the simplest solution might be to give this customer an Access
2000 MDE and let them run it under their retail copy of Access 2000 instead
of using the Access 2003 runtime.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.