I have developed a database in Microsoft Access 2013. I wish to install and run that database on another machine on which I have already installed the MS Access Runtime.
In order to allow the database to run correctly on the target machine, I need to add two Trusted Locations - one for the front-end database and another for the back-end database.
The folder paths on the runtime machine are different to those on the development machine, so how do I add Trusted Locations (on my development machine) which remain valid when the database is copied to the target machine?
Must I trick it by simply creating an identical, dummy folder structure on the development machine (would this even work?), or is there a more elegant way?
In order to allow the database to run correctly on the target machine, I need to add two Trusted Locations - one for the front-end database and another for the back-end database.
The folder paths on the runtime machine are different to those on the development machine, so how do I add Trusted Locations (on my development machine) which remain valid when the database is copied to the target machine?
Must I trick it by simply creating an identical, dummy folder structure on the development machine (would this even work?), or is there a more elegant way?