There is no obvious way to set a location as a trusted one in the packaging wizard. However, I bypassed the problem by running Access and indicating the installed program's location as a trusted location.
This is a cumbersome and ineffective process since most systems on which I intend to install the program, only have runtime versions of Access.
---In MS_Access_Professionals@yahoogroups.com, <kato.dienye@yahoo.com> wrote:
Is there a more effective way of doing this?
Thanks for your time...
Kato Dienye.
On Wednesday, February 19, 2014 8:15 AM, "wrmosca@comcast.net" <wrmosca@comcast.net> wrote:
To avoid that notice, the database file must go in a trusted location. I've never used the packaging wizard but there must be a step to set the destination folder as a trusted location.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
http://mvp.microsoft.com/en-us/mvp/Bill%20Mosca-35852
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
---In MS_Access_Professionals@yahoogroups.com, <kato.dienye@yahoo.com> wrote:
I successfully installed a packaged Access 2007 based solution on a computer that has Office 2010 installed. However, on startup, the packaged solution displays Access Security Notice (A potential security concern has been identified, etc ...). I repackaged the solution with Access 2010 and installed it and the same notice popped up at startup. Does anyone know of any way around this? Thanks for your assistance.
__._,_.___
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (4) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar