Avoiding security warning by adding digital signatrues
I want to distribute an mde file but I dont want it to come up with
"This file may not be safe if it contains code that was intened to harm your computer. do you want to open this file or cancel the operation?
Do I need digital signatures? How do I create and import them and what do they cost?
"This file may not be safe if it contains code that was intened to harm your computer. do you want to open this file or cancel the operation?
Do I need digital signatures? How do I create and import them and what do they cost?
Here are several recent and ongoing threads on EE ... some VERY good information.
https://www.experts-exchange.com/questions/22468746/Sandbox-mode-blocking-expressions-or-maybe-not.html
https://www.experts-exchange.com/questions/22470100/Signing-Access-2007-Project.html
https://www.experts-exchange.com/questions/22479658/Security-settings-in-access.html
mx
https://www.experts-exchange.com/questions/22468746/Sandbox-mode-blocking-expressions-or-maybe-not.html
https://www.experts-exchange.com/questions/22470100/Signing-Access-2007-Project.html
https://www.experts-exchange.com/questions/22479658/Security-settings-in-access.html
mx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"=SomeFunctionCall"
That would be a LOT of re-working over the last 14 years :-(
Not to mention calling functions from queries,
mx
That would be a LOT of re-working over the last 14 years :-(
Not to mention calling functions from queries,
mx
"Yes, you need a digital signature"
I'm not sure why you say that, because if you set Macro (in)Security to Low ... you can avoid the entire issue, right?
mx
I'm not sure why you say that, because if you set Macro (in)Security to Low ... you can avoid the entire issue, right?
mx
<"=SomeFunctionCall"
That would be a LOT of re-working over the last 14 years :-(>
True, but nobody said it was easy <g>. Besides, while it's used often (and even advocated by MS in some instances) the use of function calls for event procs and such is generally considered a no-no by most experienced developers. Not saying it's the right way, or the only way, but in general it seems to be frowned upon by a majority of professional Access developers. The use of function calls in queries is a bit more difficult to overcome, but it can be done.
<I'm not sure why you say that, because if you set Macro (in)Security to Low ... you can avoid the entire issue, right?>
I say that because the CORRECT way to avoid securit prompts is to follow the steps as outlined by MS to add a digital signature and prepare the enduser environment for the same. I realize it's much easier to set the security to low, but you are apparently unaware that many people CANNOT set macro security to low. The majority of my userbase, which is comprised in large part of financial, government and aerospace workers are not allowed to do so. In my case, your suggestion simply would be a non-starter. While the majority of posters here are building solutions for themselves or a very small workgroup, and could most like set the security to low, IMO suggesting they do so is akin to suggesting someone disable their antivirus to speed up boot times - it works, but it sure ain't the best solution.
That would be a LOT of re-working over the last 14 years :-(>
True, but nobody said it was easy <g>. Besides, while it's used often (and even advocated by MS in some instances) the use of function calls for event procs and such is generally considered a no-no by most experienced developers. Not saying it's the right way, or the only way, but in general it seems to be frowned upon by a majority of professional Access developers. The use of function calls in queries is a bit more difficult to overcome, but it can be done.
<I'm not sure why you say that, because if you set Macro (in)Security to Low ... you can avoid the entire issue, right?>
I say that because the CORRECT way to avoid securit prompts is to follow the steps as outlined by MS to add a digital signature and prepare the enduser environment for the same. I realize it's much easier to set the security to low, but you are apparently unaware that many people CANNOT set macro security to low. The majority of my userbase, which is comprised in large part of financial, government and aerospace workers are not allowed to do so. In my case, your suggestion simply would be a non-starter. While the majority of posters here are building solutions for themselves or a very small workgroup, and could most like set the security to low, IMO suggesting they do so is akin to suggesting someone disable their antivirus to speed up boot times - it works, but it sure ain't the best solution.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deovrsigningvbaproject.asp