- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsWhen I try to connect to the web through a program that worked for a couple of years until about a week ago I get the following error message:
VB Internal Error #-2147467259
Description: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Source: Microsoft OLE DB Provider for ODBC Drivers
When I set a break point and place the cursor over the variable it shows the correct information, but when I try to continue I then get the error.
I am open to any ideas and would appreciate the help.
Thanks...
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: wfinnPosted on 2002-03-28 at 11:02:22ID: 6903367
Hi Joe,
I recently had the same problem. In my case, the ODBC driver had been reinstalled, and the data source name had accidentally been renamed. The way to check this is to go to your ODBC administrator and under the drivers tab, find out the name of the ODBC data source. Check the name and compare it to what your program is expecting. If it is not the same, then you will need to uninstall the driver and reinstall it properly. If you do not find the driver at all, then simply installing it would work. If the driver is there and the name is correct, I would try a simple test of creating a DSN and they try to connect to it from a program like Microsoft Access. If you can't establish a connection from Access, then a reinstall of the driver may solve the problem. If you can connect, then maybe the driver is just a red herring and the problem is somewhere else.
Good luck.
Warren