Trusted Location process in Access 2007

[batteam]

Our group has a single production copy of an Access .adp application located
in a single, shared location on our server. Each time a user launches that
application, a small .mdb file copies that production .adp appliction to a
location on that user's personal drive on the server. Once its there, its
opened and launched. This ensures everyone is using the same and most recent
version of the app.

Now I see a problem coming with Access 2007 (we're still using Access 2000).
Since all our users are using the same copy of the application, but opened
from their own personal drive (on the server), how does one identify all the
user's individual drive locations on the server in the Trusted Location
process of our lone production copy, or better yet, bypass this process
altogether? We have many, many users of the app, so its not practical to
list each user's personal drive location in the Trusted Locations area of the
app.

Any advice on this is appreciated.

 

[Graham Mandeno]

Hi batteam

Trusted locations are set on a per-user, per-computer basis and are stored
in the user's personal settings of the local registry.

You can set a location as trusted either through the Access 2007 user
interface, or by creating the required registry keys, either through code or
using a .REG file.

The contents of a .REG file would look something like this:

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted
Locations\<SomeUniqueName>]
"Path"="<YourPath>"
"AllowSubfolders"=dword:00000001 <<< if you want to trust subfolders
"Description"="<MyApplicationDescription>" <<< desirable but not required

(the first line will probably wrap - everything from "[" to "]" should be on
one line)

Note that the path must be written with doubled backslashes - for example:

"Path"="C:\\Applications\\My Database Folder"

 

[batteam]

Thanks.

Looks like if we go to all the user's PC's the first time each user launches
the App, and set a Trusted Location to the path and location that the app
will launch from, using the Access 2007 user interface, we should be OK.
From what I read from your reply, the Trusted Location is set on - and stays
with - the individual PC and its Registry, NOT with the application itself.
Correct?

Hi batteam

Trusted locations are set on a per-user, per-computer basis and are stored
in the user's personal settings of the local registry.

You can set a location as trusted either through the Access 2007 user
interface, or by creating the required registry keys, either through code or
using a .REG file.

The contents of a .REG file would look something like this:

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted
Locations\<SomeUniqueName>]
"Path"="<YourPath>"
"AllowSubfolders"=dword:00000001 <<< if you want to trust subfolders
"Description"="<MyApplicationDescription>" <<< desirable but not required

(the first line will probably wrap - everything from "[" to "]" should be on
one line)

Note that the path must be written with doubled backslashes - for example:

"Path"="C:\\Applications\\My Database Folder"
--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand

Our group has a single production copy of an Access .adp application
located
in a single, shared location on our server. Each time a user launches
that
application, a small .mdb file copies that production .adp appliction to a
location on that user's personal drive on the server. Once its there, its
opened and launched. This ensures everyone is using the same and most
recent
version of the app.

Now I see a problem coming with Access 2007 (we're still using Access
2000).
Since all our users are using the same copy of the application, but opened
from their own personal drive (on the server), how does one identify all
the
user's individual drive locations on the server in the Trusted Location
process of our lone production copy, or better yet, bypass this process
altogether? We have many, many users of the app, so its not practical to
list each user's personal drive location in the Trusted Locations area of
the
app.

Any advice on this is appreciated.

 

[Graham Mandeno]

Yes, that is correct. You need to set it only once, for each user, on each
PC.

Note that it is the folder (and, if you specify the option, all its
subfolders) that is trusted, not the individual application file.

Theoretically it is possible to trust C:\ and all its subfolders, although
that would somewhat remove the whole point of trusted locations!

I see that you said in your original post:

Each time a user launches that application, a small .mdb file
copies that production .adp application to a location on that
user's personal drive **on the server**.

I would recommend you copy it to a trusted folder on the local drive. You
will get a far better performance benefit with the front-end on the local
drive and only the back-end data on the server.

--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand

Thanks.

Looks like if we go to all the user's PC's the first time each user
launches
the App, and set a Trusted Location to the path and location that the app
will launch from, using the Access 2007 user interface, we should be OK.
From what I read from your reply, the Trusted Location is set on - and
stays
with - the individual PC and its Registry, NOT with the application
itself.
Correct?

Hi batteam

Trusted locations are set on a per-user, per-computer basis and are
stored
in the user's personal settings of the local registry.

You can set a location as trusted either through the Access 2007 user
interface, or by creating the required registry keys, either through code
or
using a .REG file.

The contents of a .REG file would look something like this:

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted
Locations\<SomeUniqueName>]
"Path"="<YourPath>"
"AllowSubfolders"=dword:00000001 <<< if you want to trust subfolders
"Description"="<MyApplicationDescription>" <<< desirable but not
required

(the first line will probably wrap - everything from "[" to "]" should be
on
one line)

Note that the path must be written with doubled backslashes - for
example:

"Path"="C:\\Applications\\My Database Folder"
--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand

Our group has a single production copy of an Access .adp application
located
in a single, shared location on our server. Each time a user launches
that
application, a small .mdb file copies that production .adp appliction
to a
location on that user's personal drive on the server. Once its there,
its
opened and launched. This ensures everyone is using the same and most
recent
version of the app.

Now I see a problem coming with Access 2007 (we're still using Access
2000).
Since all our users are using the same copy of the application, but
opened
from their own personal drive (on the server), how does one identify
all
the
user's individual drive locations on the server in the Trusted Location
process of our lone production copy, or better yet, bypass this process
altogether? We have many, many users of the app, so its not practical
to
list each user's personal drive location in the Trusted Locations area
of
the
app.

Any advice on this is appreciated.

 

[batteam]

Thank you so much for you time and advice on this matter.

Yes, that is correct. You need to set it only once, for each user, on each
PC.

Note that it is the folder (and, if you specify the option, all its
subfolders) that is trusted, not the individual application file.

Theoretically it is possible to trust C:\ and all its subfolders, although
that would somewhat remove the whole point of trusted locations!

I see that you said in your original post:

Each time a user launches that application, a small .mdb file
copies that production .adp application to a location on that
user's personal drive **on the server**.

I would recommend you copy it to a trusted folder on the local drive. You
will get a far better performance benefit with the front-end on the local
drive and only the back-end data on the server.

--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand

Thanks.

Looks like if we go to all the user's PC's the first time each user
launches
the App, and set a Trusted Location to the path and location that the app
will launch from, using the Access 2007 user interface, we should be OK.
From what I read from your reply, the Trusted Location is set on - and
stays
with - the individual PC and its Registry, NOT with the application
itself.
Correct?

Hi batteam

Trusted locations are set on a per-user, per-computer basis and are
stored
in the user's personal settings of the local registry.

You can set a location as trusted either through the Access 2007 user
interface, or by creating the required registry keys, either through code
or
using a .REG file.

The contents of a .REG file would look something like this:

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted
Locations\<SomeUniqueName>]
"Path"="<YourPath>"
"AllowSubfolders"=dword:00000001 <<< if you want to trust subfolders
"Description"="<MyApplicationDescription>" <<< desirable but not
required

(the first line will probably wrap - everything from "[" to "]" should be
on
one line)

Note that the path must be written with doubled backslashes - for
example:

"Path"="C:\\Applications\\My Database Folder"
--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand


Our group has a single production copy of an Access .adp application
located
in a single, shared location on our server. Each time a user launches
that
application, a small .mdb file copies that production .adp appliction
to a
location on that user's personal drive on the server. Once its there,
its
opened and launched. This ensures everyone is using the same and most
recent
version of the app.

Now I see a problem coming with Access 2007 (we're still using Access
2000).
Since all our users are using the same copy of the application, but
opened
from their own personal drive (on the server), how does one identify
all
the
user's individual drive locations on the server in the Trusted Location
process of our lone production copy, or better yet, bypass this process
altogether? We have many, many users of the app, so its not practical
to
list each user's personal drive location in the Trusted Locations area
of
the
app.

Any advice on this is appreciated.