Linked Tables

[PaulSpell]

I have a problem with a database I am building on our server. The database is sited on a central server and a select group of users have access to the directory where the database resides.

The problem is that some users are unable to use any of the forms based on linked tables and get an error message saying that the path is not valid, even though the source of the linked tables resides in exactly the same place.

The only thing I can think of is that some users have the directory path mapped to a different drive letter than the one used to link tables. Should this matter? I thought that Access actually stored and used the full network path rather than the shortened drive letter path. Does anyone know whether this is the case?

If the problem is caused by drive letter mapping how do I get around it?

 

[RichMorrison]

Yes this problem can and often is caused by different drive letter mappings for different users to the same physical drive. //SeverName/Folder/BlahBlah/ can be assingned to the "D:" drive on Dave's desktop, the "E:" drive on Emily's desktop, etc.

The solution is to make a common drive letter mapping for ALL users. Then link to the tables with the common drive letter.

RichM

 

[PaulSpell]

Thanks for confirming the problem but it is not possible for me re-map everything for all of the users. Isn't there a more scientific way of solving this, like assigning the full network path (in code if necessary)?

 

[RichMorrison]

I think that (using a "UNC" path) depends on:
1) the version of Access you are using
2) the version of Windows on the user's desktops
3) the network operating system (assume Novell)

I use:
Access 97,
Windows NT 4.0 workstation,
some current Novell stuff.

In this combination, I think the "Link table" option in Access menus DOES NOT support UNC naming. That's my best memory.

But try it and see. Maybe it will work for you.

RichM

 

[pono1]

May I offer another slant on the subject?

\\ComputerName\ShareName\FileName.mdb

Regards,
Tim