There were a couple of different ways I discovered dealing with this problem.
One way is to write vb code that temporarily bypasses the trusted zone such as the following:
(Note: below comments were copied from here: http://bartvdw.wordpress.com/2008/03...from-vbscript/)
You have had it before: the “Open File – Security Warning”. Nice feature, but not very interesting during execution of scripts. However you may not want to turn it off.
The simple solution in VBScript has been offered by MS themselve: the SEE_MASK_NOZONECHECKS environment variable. Change it at the start of your script and restore it at the end. Plain & simple!
Sample code (same as the KB article):
set oShell= CreateObject(“Wscript.Shell”)
set oEnv = oShell.Environment(“PROCESS”)
oEnv(“SEE_MASK_NOZONECHECKS”) = 1
oShell****n “c:\ms04-038\WindowsXP-KB834707-x86-enu /quiet /passive /norestart”,0,True
Note: the **** above = . r u n (spaced out so it doesn't put in **** again.)
The Open File – Security Warning dialog box is displayed when you try to silently install a hotfix or an update by using a Visual Basic script in Windows XP Service Pack 2
The other way is to create a trusted zone for the location of the mdb (local intranet security settings) which you said you tried. This worked for me by adding in the correct location of the mdb file.
I can't say if the above 1st example will work for you (especially with 2 firewalls). I used the 2nd method above adding it as a trusted zone. I have not personally tested the script method - I only came across it while trying to get rid of the Open File Security Warning (note: you would most likely launch your mdb embedding opening the mdb within the vb script using the VB example above.)
Now if the warning you're getting refers to MACRO security within the mdb (once the mdb is launched), that's different and is fixed within MSAccess itself by changing the Macro security level under MSAccess Tools/Options.
Hopefully it helps in some way.
Last edited by pkstormy; 12-03-09 at 23:51.
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)