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.
LVL 1
BobbyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PatHartmanCommented:
I'm not sure what Access caches.  However if linking new tables using the same DSN results in no problem, I would simply delete all the linked tables and start again.
0
BobbyAuthor Commented:
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???
0
BobbyAuthor Commented:
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.
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

BobbyAuthor Commented:
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?
0
Gustav BrockCIOCommented:
Create a new 2003 mdb file, attach the tables, and see if you can open and read these at normal speed.
If so, reference the dlls and ocxs. If tables still open rapidly, import all objects from the old 2003 mdb.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Check and see if you have any mapped printers or drives that are not available.   If so, disconnect them.

  These will slow down the process that Windows goes through when dealing with network connections.

Jim.
0
John TsioumprisSoftware & Systems EngineerCommented:
Check if your settings in the workstations NIC point to the new DNS or the continue to use the old one..
0
BobbyAuthor Commented:
John, good point, but yes the workstations were already pointing to the new DNS server. Gustav's solution did the trick.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SQL

From novice to tech pro — start learning today.