Link table error for users at second location

[Guest]

I have split a database into a fe/be. Now some of the users from location A
have moved to location B. Location A is fine. Location B cannot access the
database. the network letter drive for location A is G:\ , Location B is Y:.
How can I get the fe for the people in location B to automatically update to
Y:\.

After the letter drive the remainder of the path is the same:
G:\USPC\RPS\Shared
Y:\USPC\RPS\Shared

error received for location B users:G:\USPC\RPS\Shared is not a valid path.

Note: I am new to using code. I can do the simple things.

Thanks in advance any assistance.

 

[Jeff Boyce]

You've identified why to folks at LocationB can't "see" the back-end data.
They don't share the same ... share name!

The solution is to not use ANY sharename. Instead, by using a UNC
(\\ServerName\FolderName\FileName) designation for the link, all front-end
users can see the back-end data.

To link to a UNC source, use File | Get External Data | Link..., then
navigate to the EntireNetwork option and drill down through the network,
rather than using a sharename. After you've done this in one front-end, for
all tables, deploy the newly-linked version of the front-end to all users'
PCs.

Regards

Jeff Boyce
Microsoft Office/Access MVP