ODBC connects to wrong server even after removed.

We still have a few in house applications that use Microsoft Access for the front end that uses an ODBC connection to connect to a SQL Server.  I have a 64bit computer so I removed both 32bit and 64bit ODBC connections that were pointing to my production server.  I rebooted the computer after I had removed the existing ODBC connections and then once the computer was back up, I connected the ODBC to our test server.  After several hours of testing I realized that I was in fact pulling live data from the production server even though my ODBC connection was pointing to my test server.  Any ideas?  This has happened a few isolated times.  

Thank you!
LVL 1
Jarred BeverlyAsked:
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.

JohnBusiness Consultant (Owner)Commented:
Look in Control Panel, Credentials and see if the connection profile is there and if so delete it.
0
Nick67Commented:
After several hours of testing I realized that I was in fact pulling live data from the production server even though my ODBC connection was pointing to my test server.

Access is more than capable of doing DSN-less connections through VBA code for one.
For another, the DSN is only required to create linked tables or use the Linked Table Manager to point the tables to a new locations.
The ODBC connection details for each object are stored in system tables and are not depended only ODBC saved connections on the machine.  They will work so long as the information contained in the connection remains valid.

Until you go through the linked table manager and repoint the tables at new sources, they will continue to happily work with the old sources.
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
Jarred BeverlyAuthor Commented:
Thank you John! I looked but that wasn't it.  Great idea though.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Did you check in the hosts file for any entrance for the Production server?
Also check for server alias.
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
Microsoft SQL Server

From novice to tech pro — start learning today.