|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Macro SercurityI keep setting my Option Level and "Low"...
But it keeps changing back to "Med" Hi,
this behaviour might be because of some Windows security setting. Is this your own computer or a work one? If work then they might have set up a policy which does not let you switch the macro security level. One way would be to not change to a low security level. This should be avoided anyway since it brings a security risk. Instead try to digitially sign your project. You can either do this by yourself with selfcert.exe, or you can buy one from a trusted source. If you do it yourself the macro warning will come up ones when run for the first time, but if the users enable the project for all times they will not receive the warning again. If you buy one they will not be bothered with it at all. Another solution would be to run the access install in sandbox mode, but I would suggest signing your code. HTH Good luck Show quoteHide quote "David Jaco" wrote: > I keep setting my Option Level and "Low"... > But it keeps changing back to "Med" > Does code signing add any more SECURITY than what has been outlined here in
many threads? TIA> Show quoteHide quote "freakazeud" <freakaz***@discussions.microsoft.com> wrote in message news:C0E1FA23-0911-436D-901E-6C7AA76B03E2@microsoft.com... > Hi, > this behaviour might be because of some Windows security setting. > Is this your own computer or a work one? If work then they might have set > up > a policy which does not let you switch the macro security level. > One way would be to not change to a low security level. This should be > avoided anyway since it brings a security risk. Instead try to digitially > sign your project. You can either do this by yourself with selfcert.exe, > or > you can buy one from a trusted source. If you do it yourself the macro > warning will come up ones when run for the first time, but if the users > enable the project for all times they will not receive the warning again. > If > you buy one they will not be bothered with it at all. Another solution > would > be to run the access install in sandbox mode, but I would suggest signing > your code. > HTH > Good luck > -- > Oliver > Admin Specialist & Computer Science Major @ UMD - Go Terps - :) > http://www.oli-s.de > > > "David Jaco" wrote: > >> I keep setting my Option Level and "Low"... >> But it keeps changing back to "Med" >> It adds security in so far that it allows the users of the application to
trust the source of the application. It does not add security in the sense of encrypting your data or securing your projects from break ins. It secures it in the meaning of trusting the source who provides the project/code to not cause any harm on the execution machine and it ensures the developer that no one else can go into the project, change the vba to be maliciouse and redistribute it. The application would then be unsigned and untrusted again to warn possible users. HTH Good luck Show quoteHide quote "Gary J. Dikkema" wrote: > Does code signing add any more SECURITY than what has been outlined here in > many threads? > > TIA> > > > "freakazeud" <freakaz***@discussions.microsoft.com> wrote in message > news:C0E1FA23-0911-436D-901E-6C7AA76B03E2@microsoft.com... > > Hi, > > this behaviour might be because of some Windows security setting. > > Is this your own computer or a work one? If work then they might have set > > up > > a policy which does not let you switch the macro security level. > > One way would be to not change to a low security level. This should be > > avoided anyway since it brings a security risk. Instead try to digitially > > sign your project. You can either do this by yourself with selfcert.exe, > > or > > you can buy one from a trusted source. If you do it yourself the macro > > warning will come up ones when run for the first time, but if the users > > enable the project for all times they will not receive the warning again. > > If > > you buy one they will not be bothered with it at all. Another solution > > would > > be to run the access install in sandbox mode, but I would suggest signing > > your code. > > HTH > > Good luck > > -- > > Oliver > > Admin Specialist & Computer Science Major @ UMD - Go Terps - :) > > http://www.oli-s.de > > > > > > "David Jaco" wrote: > > > >> I keep setting my Option Level and "Low"... > >> But it keeps changing back to "Med" > >> > > > 
Other interesting topics
Why is this so hard?
Securing ONE database Help - Security Issue Re: Lost ability to login to secure database Help - Security Issue - File already in Use Help with security - Please "MS Access cannot open this file.. located outside your intranet o capture username() on form Please help with 3033 Permissions on Form per Page |
|||||||||||||||||||||||
