Setting RunTime Trusted Location

[Greg]

I have a situation where users login via terminal service and a Access2007
app is started up in runtime mode. Its all the user gets to do, is run this
app. So far so good. When the app starts up, they get the security message
about it not being a trusted location.

Our users would like to see an end to the security message.

In the development environment we have set the subdirectories (where the
program is run) to be trusted. But in the user login environment, they
still get "The Message".

We have created a deployment package, and install the package, everything is
happiness. But this is still not the solution.

For this environment, a deployment package is not a solution, their is just
know way we can install a deployment package for each user. Also, the
package is a live Alpha, and going through a lot of changes, so we update
frequently; and we do not have the time to manage the users login
environment to be able to install the package, and switch it back into
secure mode with all hatches battened down again. It's to complex and prone
to human error.

Is there another way?

 

[Arvin Meyer [MVP]]

There are only 2 possibilities, well 3 if you don't use code.

1. Put a trusted location on the server and put all the user folders for the
Terminal Services app in that folder.
2. Spend the $200 to $400 every year and buy a certificate and sign your
apps.
3. Use all signed macros, with no VBA code.

My choice has always been number 1.

 

[Greg]

We implement #1, setting the trusted location for a particular folder and
its subfolders. That has not work. I think because it must be set by the
user in Access, and they can not because they are in the RunTime
environment.

Will try #2
Thank you for the suggestion.
Greg

 

[Keith]

Hi Arvin,

Can you please describe how to put a trusted location on the server as you
suggest in #1?

Thanks,

Keith