Originally Posted by
ItsMe
Managing trusted locations in a network environment is not simple. If you choose to enforce trusted locations....
If possible, I would dedicate a folder on a server for your BE file. Place the BE file one level down from the root of the dedicated share folder (in its own folder to help avoid being disturbed). Create other folders to hold files relative to the BE file(s). The registry on each client machine would then be adjusted to "Trust" the share folder and to "include subfolders". It is recommended to use the Universal Naming Convention (UNC) when linking to files from the FE. When using UNC, the registry on the client machines will need an additional edit to allow "Network Locations".
I would create another folder on the C drive of the client machines for the FE. A similar directory structure should be created and a similar edit to the registry for the FE folder(s) as you did for the BE. The main distinction is this folder is not to be shared.
When I use VBA to create files that are not Access files, I make sure to use folders that reside within one of the two locations described. VBA would create and or access a file that resides in the server share or the C drive folder dedicated for the FE.
There is more than one way to edit the registry. Here is an example of using VBA to adjust trusted locations for Access databases.