(I blanked out the name of the file here)
Many guides I found on the Internet showed this as the registery code to insert to make that go away:
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted Locations] "AllowNetworkLocations"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted Locations\Location0] "Path"="N:\\database\\" "AllowSubfolders"=dword:00000001 "Description"=""
But they forgot one key thing. This is the only way I got this to actually work on my Windows XP test machine.
Note the VBAWarnings key above? That is the deciding factor for Access 2010 Runtime to not show the warning message box on my Windows XP test machine. Your mileage may vary.Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security] "VBAWarnings"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted Locations] "AllowNetworkLocations"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted Locations\Location0] "Path"="N:\\database\\" "AllowSubfolders"=dword:00000001 "Description"=""
The AllowNetworkLocations key will allow it to apply this to files stored on a windows share.
Thank you for the good article.
ReplyDeleteDue to the experience showed in this article, I would never use Access for my business deals. Fortunately, there is a solution for such kind of issues. I read in a virtual data room review that this service can easily be a platform to perform all necessary business operations.
Thank y for this scripts, its very useful, keep going.
ReplyDeletesecurity-online.net