Results 1 to 5 of 5
  1. #1
    5 Star Lounger
    Join Date
    Nov 2004
    Location
    Wilmington, North Carolina, USA
    Posts
    1,196
    Thanks
    0
    Thanked 0 Times in 0 Posts

    'Macro' security causing error? (2003)

    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 <img src=/S/sarcasm.gif border=0 alt=sarcasm width=15 height=15> 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?
    ____________________________
    Jeremy
    "If you spend more on coffee than on IT security, then you will be hacked. What&#39;s more, you deserve to be hacked." -Richard Clarke

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: 'Macro' security causing error? (2003)

    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.

  3. #3
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts

    Re: 'Macro' security causing error? (2003)

    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.
    Regards
    John



  4. #4
    5 Star Lounger
    Join Date
    Nov 2004
    Location
    Wilmington, North Carolina, USA
    Posts
    1,196
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: 'Macro' security causing error? (2003)

    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
    ____________________________
    Jeremy
    "If you spend more on coffee than on IT security, then you will be hacked. What&#39;s more, you deserve to be hacked." -Richard Clarke

  5. #5
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts

    Re: 'Macro' security causing error? (2003)

    I revisited this again today.

    I got my <img src=/S/free.gif border=0 alt=free width=30 height=15> 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.
    Regards
    John



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •