Conflict with network drive name extension on Front End database

[Thomas]

Hi,

I have a setup with a centrally stored back end database and several
users with a locally stored front end. Each user has mapped the
central server as a network drive and a table from the central
database is linked to the front end. The problem is that when the user
maps the network drive in their "My Computer" they select the drive
name extension themselves (x: or y: etc.). In the front end the table
is linked as y: so if the user choses something else than y: when
mapping the drive there will be a network path error on opening the
front end.

Since some users may already have other netwrork drives mapped under
y: it is difficult to force them all to use the same name. Is there a
way to avoid this reference that includes the drive extension in the
path? Any other ideas for how to work around or solve this issue?
Maybe there is a way to allow the user to define what he mapped the
drive as (for example on opening the database).

Many thanks in advance!
//Thomas

 

[Douglas J. Steele]

Use a UNC (\\server\share\folder\file.mdb) rather than a drive letter when
mapping. You can do this through the Linked Table Manager by navigating to
the back-end through Network Neighborhood (or My Network Places or whatever
it's called in your version of Windows)