[AccessD] A potential security concern

Hi John,

Screw with the registry.  Or run the AddPath utility (which I suppose does 
the same thing - i.e. writes to the registry) which is very easy.

Regards
Steve

-----Original Message----- 
From: jwcolby
Sent: Tuesday, January 18, 2011 5:52 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] A potential security concern

Uh ok.  So I have to screw with the registry on a machine that doesn't 
belong to me?  And I have to
do so before the first run of my FE?

I so despise Access 2007.  A C# solution is looking better.

John W. Colby
www.ColbyConsulting.com

On 1/17/2011 10:06 PM, Steve Schapel wrote:
> Hi John,
>
> As per my note in your earlier thread, see it this helps:
> http://www.accessribbon.de/en/?Trust_Center:Trusted_Locations
>
> Regards
> Steve
>
> -----Original Message----- From: jwcolby
> Sent: Tuesday, January 18, 2011 3:51 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] A potential security concern
>
> I so despise Access 2007.
>
> I installed the run time on a VM. I then dragged and dropped the 2003 Fe 
> to the desktop and get a
> security warning. It appears I have to jump through hoops to make 2007 
> trust the 2003 FE.
>
> I don't understand the hoops. If anyone understands the hoops and can 
> explain it in a succinct
> manner please do so.
>
> Thanks,
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com