[AccessD] 2007 disables app because of

Rocky Smolin at Beach Access Software rockysmolin at bchacc.com
Wed May 28 10:37:21 CDT 2008


I agree that changing the security level globally would be a bad feature.
But is there a way to do it just for the app that's running?


Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com
www.bchacc.com
 
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Erbach
Sent: Wednesday, May 28, 2008 3:16 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] 2007 disables app because of

Rocky,

I would say that that's the case.  I thank that it really has to be a
conscious user choice to decrease the level of security for macros.
Having applications willy-nilly disabling it...well, it isn't the same as
turning off action query warnings, is it?

It just seems that it would look chancy to the user to disable a built-in
security feature just to run your application.  Would take some soothing
verbiage to reduce anxiety.

Steve Erbach


On Tue, May 27, 2008 at 6:02 PM, Rocky Smolin at Beach Access Software
<rockysmolin at bchacc.com> wrote:
> So when distributing a commercial app, this has to be in the 
> ReadMeNow.txt file?
>
> Thanks and regards,
>
>
>
>
> Rocky Smolin
> Beach Access Software
> 858-259-4334
> www.e-z-mrp.com
> www.bchacc.com
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve 
> Erbach
> Sent: Tuesday, May 27, 2008 3:12 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] 2007 disables app because of
>
> Rocky,
>
> Isn't that the same type of security message that can be permanently 
> disabled if you just go to the Tools | Macro | Security option in 2003 
> and set the security level to low ("not recommended")?  In 2007 you 
> open the "Trust Center" (oh, gawd!) and select "Enable all macros (not 
> recommended; potentially dangerous code can run)".  So after being 
> suitably chastised, you can avoid the messages for good.
>
> But programmatically?  Then the bad guys could simply put that in 
> their evil macros and then where would we be?
>
> Steve Erbach
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

No virus found in this incoming message.
Checked by AVG. 
Version: 8.0.100 / Virus Database: 269.24.1/1469 - Release Date: 27/5/2008
13:25




More information about the AccessD mailing list