signing code as a trusted designer/developer

[TracyG]

Can someone explain how to "sign" your own development code and how to put
yourself into a DB as a trusted developer/coder to avoid the macro warning
messages when security warnings settings are set from the lowest to
middle/high?

[Tom Wickerath]

Hi Tracy,

Create your own digital certificate:
http://office.microsoft.com/en-us/assistance/HP052495581033.aspx

Signing Access 2003 Projects:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmart04/html/sa04d1.asp

Code Signing Office XP Visual Basic for Applications Macro Projects:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoxpta/html/odc_dsvba.asp

MS Office 2K macro security:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deovrsigningvbaproject.asp

Rick Dobson puts a positive "spin" on the new Access Security feature in the 2nd link shown
above. I prefer Allen Browne's description:
"While I do appreciate Microsoft's push towards trustworthy
computing in general, forcing this in Access users is as
appropriate as forcing seatbeats on bicycle riders in my view."

Sent: Tuesday, February 24, 2004 4:10 PM
Subject: Re: Upgrade from Access 2K to 2K3

Another good quote comes from Gunny, in a private e-mail message that I received:

"While there are a few Access viruses in the wild, these aren't much of a hazard to the masses.
It's so incredibly hard for a competent database developer to get an Access application to run
properly on a computer with an unknown configuration. It's far more difficult for script
kiddies – who mainly copy other people's work and make just a few modifications – to produce a
viable Access virus that will run on most computers. So there's a very good reason Microsoft's
programmers put so many bugs into Access: better security!"

Tom
_________________________________

"TracyG" <mye...@email.com> wrote in message news:upc$0ms9EH...@TK2MSFTNGP12.phx.gbl...