Linked Table Direct Referencing
I have an Access XP database that is linked to another table in another MDB file. Both of these MDBs are located out on a network drive for people in different offices to use. It works great except for the following situation.
The district staff whose offices are located in other cities are connected to the network using a different drive letter. The linked table is located in a file which is located in \\Network Drive\Folder\Directory\MydB.mdb. The central office maps \\Network Drive\Folder as P:. Therefore, the file is located at P:\Directory\MydB.mdb. However, the same drive is defined as J: to the district offices. They see J:\Directory\MydB.mdb.
Problem: When you link a table in Access XP and specify the drive, it takes the P: or J:, then the directory, then the file, then the table name. Even though P: = J: = \\Network Drive\Folder, the district's attempt to open the main db fails because it's looking for a table linked via P:\Directory\MydB.mdb, not J:\Directory\MydB.mdb. The P: and J: should be irrelevant. Access should be looking for \\Network Drive\Folder\Directory\MydB.mdb... but it doesn't.
Convincing the IT people to map everyone as P: or J: is not an option. My temporary solution is to have two versions of the main MDB... one for the central office and one for the district. The central office version links to P:\Directory\MydB.mdb whereas the district's version links to J:\Directory\MydB.mdb (the same file).
Is there way to link a table and have Access XP recognize the actual location and not rely on the arbitrary mapping label of P: and J:?
Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division
__________________
Greg Serrano
Michigan Dept. of Environmental Quality
Air Quality Division
|
