Re: Problems with ado
- From: "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom>
- Date: Thu, 3 Nov 2005 18:14:17 -0000
> My computer recently crashed. After finally recovering most functionality,
I
> discovered that 1) the ado control in VB 6 no longer worked (Couldn't
create
> a connection string), and 2) Couldn't view tables in SQL2000 Enterprise
> manager (which after messing about with registrations ultimately wound up
> with me not even being able to create a registration (Error at end of
Wizard
> said "Data Source Name not found and no default driver specified).
>
> Not sure where to begin looking. The components in VB6 are registered
> properly and the files exist. In SQL, I'm mystified.
Start small. You don't need an ADO Control - yet.
You use divide-and-conquer techniques to work out what is intact, what is
damaged.
1. See if you can create a database using SQL2000 Enterprise Manager
If yes => Must be allright
If no => SQL2000 damaged, uninstall and reinstall
2. See if you can view all databases using Query Analyser, SQL2000
Enterprise Manager
If none can be seen by QA => QA damaged, uninstall SQL2000 and reinstall
+ SP4
If none all can be seen by EM => EM damaged, uninstall SQL2000 and
reinstall + SP4
If a particular database is damaged => repair or replace
3. See if VB6 can produce non-database executables
If yes => Must be allright
If no => uninstall and reinstall
4. See if you can create RecordSet to SQL Server database and/or other
databases like Access or Text file.
If all prove negative => reinstall MDAC
If some prove negative => examine providers etc.
5. If using ADO is a success but ADO control is not
=> Control must be damaged isn some way, etc.
Stephen Howe
.
- Follow-Ups:
- Re: Problems with ado
- From: bluerick
- Re: Problems with ado
- Prev by Date: Re: Problems with ado
- Next by Date: Re: Problems with ado
- Previous by thread: Re: Problems with ado
- Next by thread: Re: Problems with ado
- Index(es):
Relevant Pages
|