Hi,
I'm using a back-door method of establishing trusted locations for my
application since it runs under Access 2007 Runtime ... and I need to fiddle
with the registry to get this set up.
All seems to work ... half of the time.
I have two front-ends the user can execute. One gets the Access 2007
Security warning when attempting to open the back-end, and the other
doesn't! They use identical code to open the database. Both run from the
same folder on the user's computer, and that folder is also set as a trusted
location. The backend database for the application is in a network share.
I'm not getting an warning pointing to the front-end's folder --- just the
back-end's ... and only when executing one of the two front-ends !
I seem to be getting the security warning only when I use a network share.
The key name is "Path" and the key value is simply the network share
name --- such as \\xxxxx\folder\
I do not get the security warning when I change things around and have the
back-end on the user's computer (in a different folder than the front-ends,
but in a folder that I set as a trusted location).
So if I define a network share as a trusted location, do I need to set
something else in the registry??
Any help??
bob
Bob Howard - 25 Feb 2008 19:45 GMT
addendum ...
MS documentation on setting up trusted locations "the normal way" says
there's a setting called "Allow Trusted Locations not on the computer" that
you need to check if defining a network share in addition to defining the
share's location --- that's what was behind my initial message...
bob
> Hi,
>
[quoted text clipped - 28 lines]
>
> bob