Network Drive Reference

  • Thread starter Thread starter js
  • Start date Start date
J

js

I have a network drive mapped to E which has the db stored
on it. others users have it mapped to F, some to E, some
to P, etc.

Everyone that has it mapped to the same drive as I do is
fine, but those mapping to a different drive letter are
not able to use it.

How can I correct this?
thanks
 
Hi,

This is happening because the connection string (the one who points to
back-end database) is stored into the front-end MDB, in Connect property of
the Tabledef object
There are two ways to solve this problem:
1. Install the front end MDB to each user's PC, so each front end will work
with its own connection string, which will contains locally mapped drive.
With this approach you'll minimize also the network traffic, but when you
update the application, you have to be sure you update it on all your PC's
2. If you want to keep both front end and back end MDB's on shared drive,
you need to create your own relink procedure. It should first check if
tables are relinked, if not ask for a the path tp BE database, then, convert
it to UNC path and use UNC path in connection string. This is because all
PC's from a network are able to access the shared resource using exactly the
same UNC path (\\servername\sharename\path_to_MDB).
There is still an exception here. You won't be able to run the app on the PC
which act as server, since for it the path to the back-end is local path,
which cannot be converted to UNC.But if tyhat PC is used as a server only,
so noone works on it, you won't have this problem.

If you have any further questions, you can contact me.

HTH,
Bogdan Zamfir

________________________
Independent consultant
 
If you can't standardize the mapping on the network, then
you can use the UNC path to the database by browsing Network
Neighborhood for the db in the Link Table Manager...

\\ServerName\SharedFolder\YourDB.mdb

This will be the same for all.

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________
 
Are you using linked tables within the database, and Access
can't find the data because it's not on their E drive? If
so, you can use UNC paths. That is, instead of using
E:\directory\myfile.mdb, use
\\servername\path\to\directory\myfile.mdb. To do this when
linking the table via the GUI interface, find the file in
Network Neighborhood (or its equivalent) rather than on E:\
drive.

If you're starting the database from a batch file or
script, you just need to use UNC paths there too.

If neither of these are the problem, what exactly do you
mean when you say "those mapping to a different drive
letter are not able to use it"? What error do they get?

--chris
 
bzamfir said:
This is happening because the connection string (the one who points to
back-end database) is stored into the front-end MDB, in Connect property of
the Tabledef object
There are two ways to solve this problem:
1. Install the front end MDB to each user's PC, so each front end will work
with its own connection string, which will contains locally mapped drive.
With this approach you'll minimize also the network traffic, but when you
update the application, you have to be sure you update it on all your PC's
Click to expand...

But what happens when you have updates for the app?

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the utillity see
the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

Also see relink Access tables from code
http://www.mvps.org/access/tables/tbl0009.htm
2. If you want to keep both front end and back end MDB's on shared drive,
you need to create your own relink procedure.
Click to expand...

You don't want to have folks sharing the FE as this has an increased
chance of corruption. Especially in A2000 and newer.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
I have a drive mapped as F:, this drive was mapped originally to my main
domain server and the data directory on that domain. Recently the F: drive
reported it could no longer see the network. When I tried to disconnect the
drive, nothing happened. I cannot disconnect the drive. I have mapped the
same directory as g: and have no trouble accessing that data. The f: drive
still exists, and thinks it's a physical drive now!!! anyone? what the
%^&$ is going on. This is on a XP pro workstation.

regards,
 
I haven't experienced this problem, but I think that posting
to one of the XP newsgroups would be more effective than the
Access group. Did you get everything working with the UNC's?

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________
 
Back
Top