‘Macro’ security causing error? (2003)

Topic

New Reply

I designed my database in A2k, and am now putting it on machines with 2k3. It seems that while I’m going through all 3000 warning messages that the database I’m opening contains potentially unsafe code, some objects are loading, while others aren’t. The ones that load are dependent upon some that aren’t (i.e. a list box that relies on a text box for a filter), I then get an error prompting for the text box value. I’ve found that changing macro security to low alleviates this problem, and as much as I’d prefer to keep the security at medium or high, until I can convince the Marine Corps to pay for me to be able to smack a certificate on the database this is what I have to do. Any suggestions/anyone with similar experiences/workarounds?

Reply | Quote

Replies

I don’t have/use Access 2003, so I cannot help, but you may find Microsoft Office Assistance: Frequently asked questions about Access security warnings useful.

Reply | Quote

Jeremy

If you set the security back to medium, and answer “yes” to the question about Access running in Sandbox mode then it seems to work.
Having done this, I now get just one security warning when opening instead of several.

If I signed the database, then I presume this one warning would go away.

I found this link which claim that you can get a free signature suitable for signing VBA macros at CACert.org. I tried this the other day, but when I tried to use it, Access said it could not verify the certificate, so it did not accept it.

I will try again. I was not sure what I was doing at any stage of the process, so I may have done wrong the thing.

Reply | Quote

John,
Thanks for the link – as it’s approaching midnight, I’m going to go to sleep, but I will check your link out first thing in the morning… I’m sure by then one of the admins/wmvp’s will shed some more insight into that claim. Thanks again

Jeremy

Reply | Quote

I revisited this again today.

I got my certificate from CA and installed it in IE. I then also installed the CA root certificate (available from the CA website) into IE as well.

From what I read this puts both of them in the windows store of certificates. The root certificate enables verification of my own certificate.

Now I can sign the code in my databases, and open them on my machine without any warnings at all. (For the first one I said to always trust that certificate).

I don’t know what will happen on another machine, but at least I can have my own security set to medium, and not receive any warnings at all.

Reply | Quote