Linked tables - error 3044 - not a valid path

[cmohr]

I have linked tables that all link to a single database on the C: drive. When I relinked them to a network drive, the network link seems to have gotten stuck somewhere and when I relink to the database back to the C: drive, one of the tables stays linked internally somewhere to the network drive, even though the link manager says it isn't linked to the network drive. I have tried relinking when the network drive is online and it relinks to c:, but if I disconnect the network drive, the table is still linked to it somewhere internally and gives me the error message "<Path> is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. (Error 3044)"
There isn't anything in the code that points to the network drive. I can't get past this…Help!

 

[Remou]

Have you tried deleting the linked table? That is, choosing delete when the object is a linked table deletes the link, not the table itself. After deleting, you can re-link using File->Get External Data->Link Tables.

It is also possible to change or examine the connect property of a table.

Here is some information:

http://msdn2.microsoft.com/en-us/library/bb243197.aspx

You will find more in Help.

 

[Hap007]

Hi cmohr,

You may want to examine both backends for the table you are having problems with.

The table in question might not exist in both databases, or the spelling may have changed.

Hap...

Access Developer

http://www.fcs-software.com/fcsaccessdev.html

Access based Accounting Solutions - with free source code
Access Consultants forum

http://www.tek-tips.com/threadminder.cfm?pid=1121

 

[cmohr]

Thanks for the information and the link to change or examine the connect property of a table - very handy!. I didnt know that you could delete the link like that, although it seemed that there should be a way to do it and unlink the tables. I ended up creating a new database and importing everything from the old one to reset what may have gone awry.
The backend was exactly the same in both places - to be sure, I had just replaced the back end that was a problem with the one from the network drive and it still told me that it was looking for that one errant table out of the bunch on the other drive.
Thanks for all of your help! I am back on my way again.