I have developed a split database for a client although there is currently only a single user. The path to the back end on the client machine is similar to C:\Program Files\Database\BE.mdb. This path can be recreated on my machine in my office so I can easily work on the front end and send it back with no table linking issues. The client now wants to add a user and put the back end in a shared folder on a server. I guess that the path to the back end will now be via a mapped drive letter or a UNC such as \\server\database\BE.mdb. If the client sends me the front end I can change the link path to a local drive on my machine in order to work on the file but the client would then have to relink to their server drive when I send the file back. Is there any way to "create" a network path on my machine which is the same as the client's in order to avoid them having to relink when I send the file back??