I don't think you'll like this...

[Nightowl4933]

...but I would like to find a solution to this inconvenience...

My database runs on the work's network and the tables are mapped to a back end database.

I develop the database at home, so I was hoping to set up a directory structure so any changes I make to the front end will only need me to replace the existing FE with the new one, and not having to re-link tables using the Linked Table Manager.

I have very little understanding of networks, but the Linked Table Manager shows the filepath as:

Z:\Main Folder\Next Folder\Another Folder\db Data\Database - Release v1.1_BE.accdb

It's probably not a brilliant idea, though!

Thanks

 

[Ranman256]

You MUST relink if you are home and cannot connect to the server path.
This way you can make all the changes at home then bring them in later.
Ten Relink to sever path, back in business.

 

[arnelgp]

what you need is a relinker. see the code in the db.

 

[Galaxiom]

A folder on a PC can be mapped to a drive letter so it would work.

However I prefer to use the UNC share in a network because it saves worrying about consistent mapping on all the users PCs.

The other thing I do is use a hidden share. Append a $ character to the share name and it won't be listed in the Network resources. This one step protects the back end from casually nosy users. A further protection can be afforded by configuring the clients to stop them browsing UNC paths. This can be done in Group Policy on a domain.