Unable to delete table link

[Leif]

I have Access 2000 running on Windows 2000.

I established a link to another Access table. However,
after doing so I could not bring up the table. Access
either displays the table nor gives an error message.
I've tried deleting the link and Access ignores that.
I've tried restarting Access, same result. I've tried
doing a compress and repair, same result. I've tried
rebooting my computer, same result.

Has anyone seen this? Is there a fix?

Thanks,
Leif

 

[Wayne Morgan]

It sounds as if something got corrupted when you tried to link the table.
The easiest thing may be to create a new, blank database file and import the
objects from the current file, except for the bad linked table.

 

[Guest]

Thanks Wayne for your reply.

I think the problem is an Access bug rather than
corruption.

If I open a new Access database, and link to that table
(or even a different table in the same db), I get the same
problem. If I open the db I'm trying to link to I can
open and view the table, no problem. I even tried doing a
repair/compress on the target db with the same results.

I did a little further investigation. I have a copy of
the target db. This db is db level password protected.
If I link to the db with the password set it works, no
problem. However, after I remove the db password from the
database, then try to link to it, I experience the
problem. So, it seems related to the password protection.

Regards,
Leif

 

[Wayne Morgan]

If you create a link to a password protected database, the password gets
stored with the link information, so if you open that table again, the
password will be passed automatically. To change the password, the easiest
thing to do is to delete the linked table and create a new link.

 

[Guest]

Thats the point, Access does not allow me to delete the
link to the table. Not only that, but I've noticed that
once I try to open the table (through the link, and that
fails), and I close Access, Access remains in memory. In
fact, according to task manager, Access is using around 50-
60% CPU, even though it appears not be running.

 

[Wayne Morgan]

Did you try importing into a new database file to see what happens? I've not
heard of this problem before and usually when strange things such as this
happen, it is a corruption problem.