Trusted Location Problem

[pas926]

I'm using MS Access 2007 and when I try to enter a trusted location on our
network I get the following error, "The path you have entered cannot be used
as a Trusted Location for security reasons. Choose another location or a
specific folder."
The only trusted location I have now is "C:\Program Files\Microsoft
Office\Office12\ACCWIZ\" I do have the "Allow Trusted Locations on my
network (not recommended)" checked. Any help with this would be appreciated.
Thanks!

 

[Tom van Stiphout]

On Tue, 16 Jun 2009 15:18:01 -0700, pas926

There should not be a need to set a network location as a trusted
location. Reason is that you should per best practices have split the
application in a front-end (FE, everything but tables, and linked
tables) and back-end (BE, tables) with the BE on the server (no need
for trusted location for the BE) and the FE on each user's workstation
(add that location to the Trusted Locations.
It seems you are trying to circumvent these best practices. If so, tar
& feathers will be in your immediate future.

-Tom.
Microsoft Access MVP

 

[pas926]

Thanks for the answer Tom I appreciate it!

On Tue, 16 Jun 2009 15:18:01 -0700, pas926

There should not be a need to set a network location as a trusted
location. Reason is that you should per best practices have split the
application in a front-end (FE, everything but tables, and linked
tables) and back-end (BE, tables) with the BE on the server (no need
for trusted location for the BE) and the FE on each user's workstation
(add that location to the Trusted Locations.
It seems you are trying to circumvent these best practices. If so, tar
& feathers will be in your immediate future.

-Tom.
Microsoft Access MVP

 

[Aaron Reichow]

I found this thread when googling about for an answer to my question- which
is the same as pas926's.

I'd ask it again: is there a way I can add a network location as a Trusted
Location? Or better yet, turn off the entire kludge of "Trusted Locations"
entirely? At least for Access?

Tom, your answer doesn't entirely hash. In my case, the reason for setting
up a network location as a Trusted Location has nothing to do with where the
back-end lives. Instead, the Access file containing our front-end resides on
our file server. A few different folks might need to open the MDB and make
some changes to the VB or the forms within, and more importantly we want our
end-users to be opening the newest version of the MDB, not whatever old
version they copied to their desktop last.

If anything, it's seems like circumventing best practices to fall into the
trap of having 11 divergent versions of a file spread between 10 different
individual PCs and the office file server.

I'm surprised by this- it's 2009, not 1989. Having multiple people work on a
single file stored on a central file server on the office Intranet is pretty
darn common.

Any ideas for how to work around this limitation?

Thanks!
Aaron

 

[Gina Whipp]

Aaron,

Answers in-line...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

I found this thread when googling about for an answer to my question- which
is the same as pas926's.

I'd ask it again: is there a way I can add a network location as a Trusted
Location? Or better yet, turn off the entire kludge of "Trusted Locations"
entirely? At least for Access?

Tom, your answer doesn't entirely hash. In my case, the reason for setting
up a network location as a Trusted Location has nothing to do with where
the
back-end lives. Instead, the Access file containing our front-end resides
on
our file server. A few different folks might need to open the MDB and
make
some changes to the VB or the forms within, and more importantly we want
our
end-users to be opening the newest version of the MDB, not whatever old
version they copied to their desktop last.

I'm not sure why end users would need to make changes to the forms, however,
they couldn't do this while anyone was in the same front end. What should
happen si there is one development copy that changes are applied to and then
it is distributed to the end users. You could use...
http://www.granite.ab.ca/access/autofe.htm This utility is GREAT and
recommended by most.

If anything, it's seems like circumventing best practices to fall into the
trap of having 11 divergent versions of a file spread between 10 different
individual PCs and the office file server.

I cannot begin to answer this question as I do not allow end users to make
modifications. I have the development copy and all changes are applied to
it. When I want to run out updates I 'connect' and drop my latest one in
place. In one case I drop it in and a batch file runs when they log into
Terminal Services and if their front end needs updating it happens during
the log in process.

I'm surprised by this- it's 2009, not 1989. Having multiple people work on
a
single file stored on a central file server on the office Intranet is
pretty
darn common.

Perhaps this is common in your world but in the Access world it is not
common. Sharing a front end is HIGHLY frowned upon.

For information about splitting and why you should split....

http://allenbrowne.com/ser-01.html
http://www.members.shaw.ca/AlbertKallal/Articles/split/