Linked table manager looking at the wrong location

[M Skabialka]

On a FE/BE Access 2007 database the IT team asked me not to use a mapped
drive letter but the server name and path (UNC) when linking tables. I
changed the link to point to location \\server2\data and copied the FE to
three computers. They logged off, went home and came back today and the
database doesn't work, error 2467 which turned out to be that it couldn't
find the tables. I looked at the linked table manager and instead of the
UNC they show Z: as the drive location.
What happened?

 

[Douglas J. Steele]

How did you change the linkage in the first place?

If you're going through the Linked Table Manager, navigate to the back-end
via Network Neighborhood (or whatever it's called in the version of Windows
you're using)

 

[M Skabialka]

I had to go over and check it at the user location - apparently there was a
drive mapping to Z: which I did not notice and used incorrectly.
I screwed up!
Mich :-(

 

[Armen Stein]

I had to go over and check it at the user location - apparently there was a
drive mapping to Z: which I did not notice and used incorrectly.
I screwed up!
Mich :-(

Hi Mich,

If you want a more automated approach to relinking tables, you're
welcome to use our free J Street Access Relinker at:
http://www.jstreettech.com/downloads

Once your links are established, it's a lot easier than Linked Table
Manager. And it easily handles using a UNC (\\) path.

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

 

[M Skabialka]

My problem is that where I develop I use drive letters, where it is used
they use the UNC. Since it is relinked only when I bring the latest copy
over, I don't really need any utilities for this.
But thanks anyway.