If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Linked table to mapped network drive
I have several access databases that feed off the same table in what I have
as a master dbase. Instead of putting my hundred different queries in one dbase, I have separated by type into 20 or so diff dbases with a linked table back to the master dbase. Problem is that these dbases are held on a network and several different users have the ability to use these dbases. These different users have different mapped drives for their network setup based on number of cd drives, etc. In Access it appears that the linked table manager is specific as to what the drive letter is called when working within a networked computer. Without refreshing the linked tables each time a different user wants to use the dbases is there a way to have the dbases universally recognize the linked tables so that no matter what a networked users maping looks like they can run the qureies and such without the need to refresh the table links? |
#2
|
|||
|
|||
If you want to add a linked table, try typing or pasting the UNC file path in
front of the file name in the Link Table dialog box. Access will then use the UNC path for the linked table rather than the drive mapping & relative path of the current user. Or, on the other hand, you could instead specify the UNC path/filename in the source database field of the query properties in each of your queries and not link to the tables at all. This will be a little more work if you will have a lot of queries though, because you would have to paste the path for each query. But, on the other hand, it allows you to browse all tables of another database, which can be an advantage if you want to use a table only once and don't want to establish a linked table. Of course, it also limits you to selecting only tables from the source database (including those linked to it), instead of being able utilize linked tables from a variety of databases. Each method has pros and cons beyond what I have listed here. I use both methods depending on the particular situation. HTH, Ted Allen "Zattack" wrote: I have several access databases that feed off the same table in what I have as a master dbase. Instead of putting my hundred different queries in one dbase, I have separated by type into 20 or so diff dbases with a linked table back to the master dbase. Problem is that these dbases are held on a network and several different users have the ability to use these dbases. These different users have different mapped drives for their network setup based on number of cd drives, etc. In Access it appears that the linked table manager is specific as to what the drive letter is called when working within a networked computer. Without refreshing the linked tables each time a different user wants to use the dbases is there a way to have the dbases universally recognize the linked tables so that no matter what a networked users maping looks like they can run the qureies and such without the need to refresh the table links? |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Table Wizard Does Not Set Relationship if Foreign Key and Primary Key Name Do Not Match Exactly in Case. | HDW | Database Design | 3 | October 16th, 2004 03:42 AM |
Office XP hangs when doing a "Save As" to a network drive | bc | General Discussions | 0 | August 12th, 2004 07:55 PM |
Complicated Databse w/many relationships | Søren | Database Design | 7 | July 13th, 2004 05:41 AM |
Linked table getting Application Error | Eric | Mailmerge | 3 | June 13th, 2004 11:08 AM |