Linked Table Manager Errors

[Bruce Powers]

I split an Access 2007 database into FE & BE. I run the BE on a network
server and the FE installed on each desktop. Everything has been working
fine. I am trying to do more development so I copied the BE data to my local
machine so I can use it as test data while performing development on the FE.
When I run linked table manager, 3 of the 13 tables cause an error. The
error says the path is not found and it shows the path of the old server
location, not the new location I specified. The other 10 tables worked fine.
I tried to delete the links on these three tables and then import them as
linked tables from the local BE copy. It appeared to work fine, and if I
float the pointer over the linked tables in the Navigation Pane it shows the
address for the local copy, but if I try to open the table, it looks for it
on the server and gives the same invalid path error. I hope someone has an
idea how to fix.

 

[AFSSkier]

I've experienced what you're going through before. What I had to do was
relink each table one at a time with the Linked Table Manager. By forcing
"Always prompt for new location" usually links the table where you want it.
But so should deleting the old tables & linking (not import) to the local
tables.

 

[Bruce Powers]

Hi Kevin,

Thanks for your sugestion. I just recopied the FE agian and tried to link
the tables one at a time using Linked Table Manager. Everything was fine
until I got to one of these 3 problem tables. As soon as I tried to link any
of them, it came up with the same error (\\server\path\be_filename.accdb is
not a valid path). It looks like it is trying to link back to the original
path, even thorugh I navigate to the new local table - UGH!

 

[AFSSkier]

Sorry I wasn't any help. Next, I would create a test db & try to link just
those 3 tables first. It that works, bring the others in.

If that doesn't work, as they say, "A fresh REBOOT will fix most of your PC
problems!", lol.

 

[Bruce Powers]

lol - thanks for the ideas, I will try

Sorry I wasn't any help. Next, I would create a test db & try to link just
those 3 tables first. It that works, bring the others in.

If that doesn't work, as they say, "A fresh REBOOT will fix most of your PC
problems!", lol.

 

[John W. Vinson]

Thanks for your sugestion. I just recopied the FE agian and tried to link
the tables one at a time using Linked Table Manager. Everything was fine
until I got to one of these 3 problem tables. As soon as I tried to link any
of them, it came up with the same error (\\server\path\be_filename.accdb is
not a valid path). It looks like it is trying to link back to the original
path, even thorugh I navigate to the new local table - UGH!

Be sure that Tools... Options... General... Track Name Autocorrect is turned
OFF. This feature has richly earned the name Track Name Autocorrupt.

Compact the database after you turn it off, if it's on. Then I'd try deleting
the three bad table links and using File... Get External Data... Link to link
to them (navigate to the backend via Network Neighborhood rather than MY
Computer).

 

[Bruce Powers]

BINGO!
Thanks so much John, did all steps as you outlined and it fixed the problem.
This has beed driving me crazy, now I can move on to more productive items.

 

[AFSSkier]

John,

What are the pros/cons of having the "Track Name Autocorrect" turned off/on?
Especially on a shared network, where several users are in & out of it
querying, adding, deleting data?

Also, does the FE (client PC) & the BE (shared network) have to be set the
same? Or can one be on & the other off? If so, which one should be off?

I read MS help on it, but respect your personal opinion.
http://office.microsoft.com/en-us/access/HA102564131033.aspx#1.

 

[John W. Vinson]

BINGO!
Thanks so much John, did all steps as you outlined and it fixed the problem.
This has beed driving me crazy, now I can move on to more productive items.

Glad I was able to help!

 

[John W. Vinson]

John,

What are the pros/cons of having the "Track Name Autocorrect" turned off/on?
Especially on a shared network, where several users are in & out of it
querying, adding, deleting data?

Name Autocorrect does not have any effect on data at all. It tracks the names
of Forms, Controls, Tables, etc.; when you (say) change the name of a Table,
it's supposed to change the name everywhere that table is referenced.

It's FULL of bugs.

I *always* turn it off and recommend that others do also. There might be some
folks who'd argue for it but I haven't seen much positive about it in these
groups.

Do note that you should ALWAYS use a split database for shared use. Having
multiple users all logging on to the same (unitary) database is a recipe for
corruption, bad performance, bloat and lockups. Instead, use Tools...
Utilities... Database Splitter Wizard to split the database into a backend
containing just the tables and a frontend with links to the backend, forms,
reports, queries and code. Each user gets a copy. Evidently you're doing so
but just wanted to emphasize this for the lurkers!

Also, does the FE (client PC) & the BE (shared network) have to be set the
same? Or can one be on & the other off? If so, which one should be off?

They should both be off. It's irrelevant for the backend and (again, in my
experience) harmful in the frontend.

 

[AFSSkier]

John,

As always thanks for your help!

Kevin

Name Autocorrect does not have any effect on data at all. It tracks the names
of Forms, Controls, Tables, etc.; when you (say) change the name of a Table,
it's supposed to change the name everywhere that table is referenced.

It's FULL of bugs.

I *always* turn it off and recommend that others do also. There might be some
folks who'd argue for it but I haven't seen much positive about it in these
groups.

Do note that you should ALWAYS use a split database for shared use. Having
multiple users all logging on to the same (unitary) database is a recipe for
corruption, bad performance, bloat and lockups. Instead, use Tools...
Utilities... Database Splitter Wizard to split the database into a backend
containing just the tables and a frontend with links to the backend, forms,
reports, queries and code. Each user gets a copy. Evidently you're doing so
but just wanted to emphasize this for the lurkers!


They should both be off. It's irrelevant for the backend and (again, in my
experience) harmful in the frontend.

 

[Bruce Powers]

Hi John,

I thought the problem was fixed, but as soon as I disconected from the
network, it gives the same error. I can open all of the tables in the local
copy of the BE database without any problems. When I open up the FE and
float the pointer over the names of the linked tables, it shows the path to
the local BE database. If I try to open the tables from the link, all open
OK except these 3. When I try to open any of the 3, there is a slight delay,
and then an error showing the old server location and saying it is an invalid
path. It seems to still try and search for these tables on the server copy
of the BE database.

 

[David W. Fenton]

What are the pros/cons of having the "Track Name Autocorrect"
turned off/on?

There are no PROS of having it turned on.

There is a whole universe of CONS.

TURN IT OFF.

(along with COMPACT ON CLOSE, another of the useless and downright
dangerous "features" introduced in A2000).