Hi Richard and thanks for the suggestion.

Yes, one of the things I already tried. Access doesn't allow me to enter the UNC Path in the Unbound Objects Source Doc property - I get the error 'The setting you entered for this property isn't valid'.

I also tried the UNC in the Unbound Objects Source Item, but whilst Access 2010 accepts this as an entry, when I run the database at a different location, (different drive letter for the back end but exactly the same path \\MyDB\CustomerDocs\Footer.doc), access 'remembers' the original Footer.doc content and does not pick up any changes made by the customer; though it works just fine on the PC/Network I created it on.

Strange that Access 'remembers' the original content even though it is most definitely linked and not embedded, even if I delete the file Footer.doc at the remote site.

I have to split the database here on my own network as the user locations don't have full blown access and are using Access Runtime 2010 - not sure if that is making a difference.

---

Reply from Richard Rost:

That's interesting. This is one of those problems that I would have to play with myself to figure out for you. If the users have a different network structure on their end, you could always ship out a new front-end with NO linked tables and then just make them a button to programmatically link the tables once the new database is in place. I cover how to do this in my SECURITY SEMINAR.