asked on

Access 2003 mdb won't open linked tables after local LAN DNS server switch

Access 2003 mdb with a SQL 2014 backend. We recently changed DNS servers on our LAN to a new box with a new name and IP address, and now the ODBC linked tables to SQL take forever to open. Is there something in an mdb that remembers it's LAN DNS server? I already tried relinking a few tables with the linked table manager, no difference. I do know, however, that the ODBC DSN is fine because I created a test mdb and added a few linked tables from the same SQL backend, and they open lightning fast. It's just something about this existing mdb that now won't open tables in a tolerable time.

SOLUTION

PatHartman

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Bobby

ASKER

Thanks. Hey, I am just now noticing that even local tables, not linked, take the same forever to open. So, it's not just linked tables.

wth???

Bobby

ASKER

and, linked tables using a different DSN (an ODBC tour our MySQL web server offsite) also take forever to open. These are all tables with hardly any records, btw.

So, it's an issue opening ANY table no matter if it's linked or not.

Bobby

ASKER

and, it's just this ONE mdb. I have a few others that have some of the exact same linked tables to SQL and they open just fine.

This mdb has been around since 2003, and the DNS server that has been retired did exist when this mdb was created, if that makes a difference, but I don't see how.

There are about 6 dll's and a couple .ocx's that I had to register with Windows when i installed this mdb back in 2003 , but.... maybe I need to re-register them?

ASKER CERTIFIED SOLUTION