Re: Problems with ado
- From: "bluerick" <bluerick@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 3 Nov 2005 10:35:01 -0800
Well, at this point in time, I can't get even that far.
Within odbc administrator, I can't create a new DSN, since no drivers show
up, and if I try to re-configure any of the dsn's I used to have, I get an
immediate message telling me that the setup routines for whatever driver I
want to use cannot be found, and to re-install it (I don't know where to find
these drivers, incidentally). That message is followed by one that says the
component was not found in the registry. (Yes, I have used some registry
repair tools, to no avail.)
If I were able to find and re-install the drivers I need (Jet 3.5 & 4 and
SQLOLEDB), I wouldn't have the first idea of how to make sure that the
components WOULD be found in the registry.
Tks for your interest and time,
Blessings,
Rick
"Paul Baker" wrote:
> What is the connection string that you are using?
>
> Paul
>
> "bluerick" <bluerick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:369C6774-621B-49DC-8DB8-CD471F570BBB@xxxxxxxxxxxxxxxx
> > Sorry about the "Well I would if I could" reply. I've tried so many things
> > recently, I didn't recall that, yes, I have done that (for mdac 2.6). The
> > install said it was successful.
> >
> > At this point in time, installing SQL server or using ODBC data sources to
> > try setting up data sources all return similar messages regarding that
> > they
> > can't find any odbc drivers. The driver list in odbc administrator is
> > empty.
> >
> > Tks again to whomever can help.
> >
> > "MP" wrote:
> >
> >> "bluerick" <bluerick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:22B2EB77-CFFD-445E-9741-226E4C0A825C@xxxxxxxxxxxxxxxx
> >> > 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.
> >>
> >> I'm just a beginner so sorry if this is way off base, but did you re-run
> >> your current version of mdac_typ.exe?
> >>
> >>
> >>
>
>
>
.
- References:
- Re: Problems with ado
- From: MP
- Re: Problems with ado
- From: Paul Baker
- 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
|
|