Setting trusted locations programmatically

[sportsguy]

When I release my small database application into corporate usage, the database will be creating a local back end, and has two server repositories which it will pull and push. Most will not have any folders marked as trusted, and certainly not if they put the database on a local server, and all will not have the new server share set to trusted.. .

any programmatic ways of adding trusted locations, so that technophobes don't have to go through the process, but it happens for them at set up?

thanks in advance

sportsguy

 

[boblarson]

You can create a batch file to add a set of registry entries. The entries that need to be added are here.

 

[sportsguy]

hmmm. . .

with everyone's desktop under a different user/logon name,
or can access call the bat file file, and pass parameters somehow?
I won't know where they will put the server backend locally. . .

the issue is that mgmt doesn't want the users to have to click any type of security buttons. and starts with the assumption the users are pc ignorant.

ugh!

this is not happening like it does on Criminal minds. . .

ever notice garcia's fingers are not typing anything intelligent?

 

[boblarson]

The backend doesn't have to be in a trusted location unless you are opening it from outside of the frontend. The registry entry needs to go to the HKeyCurrentUser so it matters not what the current user is. I believe the registry entry could use %HomeDrive% as the path instead of a direct path to the user's My Documents folder if that is what is concerning you.