Getting round security warnings for task scheduler

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We use Tack sceduler in MS 2000. Some of our jobs are Access databases.
Unfortunatly, the security warnings generated by Access when it starts up
cause the jobs to hang up, demanding user intervention.

Is there any way around this other than settings tools / macro / security to
'low'?
 
We use Tack sceduler in MS 2000. Some of our jobs are Access databases.
Unfortunatly, the security warnings generated by Access when it starts up
cause the jobs to hang up, demanding user intervention.

Is there any way around this other than settings tools / macro / security to
'low'?

Check this page: http://office.microsoft.com/en-us/access/HA011225981033.aspx#180

There are several relevant topics, eg #18 ...



Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com
 
I have looked at the MS help pages but not found a solution. Even if I
enable sandbox mode to stop the "Unsafe expressions are not blocked" message
from appearing (and I would prefer not to have to use sandbx mode) I am still
faced by a message of form:

Security Warning

Opening "path\filename"

This file may not be safe it it contains code that was intended to harm yuor
computer.
 
I have looked at the MS help pages but not found a solution. Even if I
enable sandbox mode to stop the "Unsafe expressions are not blocked" message
from appearing (and I would prefer not to have to use sandbx mode) I am still
faced by a message of form:

If you don't want to use sandbox mode, then you'd have to set the Macro Security to Low ... and you wanted to know if
there was another way around that path, so basically you either (a) enable Sandbox mode and then setup your app
correctly or (b) set Macro security to Low. Of the two (b) is easier but (a) will be more secure. Of course there is
plenty of disagreement regarding whether the Macro Security stuff is worth the time and effort, but so long as it's in
place you'll have to deal with it.

If you enable Sandbox mode, you'll also need to sign your code with a digital certificate. You can create a
self-certificate, however if you're going to distribute your code then that's not a good idea since many (if not most)
people would NOT accept a self-cert. You can purchase one from one of the online vendors (I got mine from Comodo:
www.instantssl.com)

After upgrading your workstations to Jet SP8 and attaching your digital cert to your VBA project, you would then deploy
it. The first time your project is opened, Access would prompt the user to install your cert, and would then ask them to
approve your app ... after they do this your app will open normally. If you make changes, however, they must again
approve your app (as long as the same cert is used, they won't have to re-install the cert).

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com
 
Scott

Thank-you very much for your help. I can't set Macro Security to Low (the
way in which Access has been installed onto our PC's won't allow it) and so
will give the digital certificate route a go.

Cheers

Andy
 
Back
Top