Connection problem

[Lilian]

Hi!
I have I problem with connection to back-end file. Users have used db for
approximately 6 months. It was no problems now efter were made changes on
server( the letter was changed ) where is located back-en file apppears
problems. After installation on other users computers come error message "the
path is not valid" and after I made reconnect front end to back end file the
db is only working on one computer. On the db link manager i saw that in the
path to back-end file begin disappear maps names . So now db is only working
on only one user computer. Do somebody knows how to solve this problem ?
Best regards

 

[Klatuu]

It is always better to use UNC paths rather than Drive Map paths to avoid
exactly the problem you are experiencing. In addition, in some locations,
the drive mapping may not be the same for all users. A UNC path points
directly to the server name and folders. So instead of something like:

Q:\AccessApplications\MyGreatApp

you would use

\\ServerName\AccessApplications\MyGreatApp

 

[golfinray]

As Dave suggests, the UNC path is always best. Do that checking the box at
the bottom of the linked table manager that says "always prompt for new
location." Then give the full path to that table.

 

[Armen Stein]

Hi!
I have I problem with connection to back-end file. Users have used db for
approximately 6 months. It was no problems now efter were made changes on
server( the letter was changed ) where is located back-en file apppears
problems. After installation on other users computers come error message "the
path is not valid" and after I made reconnect front end to back end file the
db is only working on one computer. On the db link manager i saw that in the
path to back-end file begin disappear maps names . So now db is only working
on only one user computer. Do somebody knows how to solve this problem ?
Best regards

In addition to the good UNC suggestions, you're welcome to use our
free J Street Access Relinker at:
http://www.jstreettech.com/downloads

It handles multiple Access back-end databases, ignores ODBC linked
tables, and can automatically and silently relink to back-end
databases in the same folder as the application (handy for work
databases or single-user scenarios). There's a ReadMe table with
instructions.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com