"Andre Gibson" <AndreGib***@discussions.microsoft.com> wrote in message
news:0A44BD42-C1EB-45E0-990D-A329D0EBEE1D@microsoft.com...
> Hello All,
>
> I am getting an error any time I try to adjust my Data Source (ODBC)
settings.
> Actually I am unable to open any of the DSN connections under User DSN and
> System DSN.
>
> Whenever I try I get this error" The setup routines for the Microsoft
Access
> Driver (*.mdb) ODBC driver could not be found. Please reinstall the
driver."
>
> Upon clicking ok that error is quickly followed by "Component not found in
> registry".
>
> How do I reinstall these drivers?
> And how did I screw up so badly to begin with?
>
> I have this error with every ODBC entry I have on this system.
>
> Any assistance would be greatly appreciated.
>
> Andre
>

"Ralph" wrote:

>
> "Andre Gibson" <AndreGib***@discussions.microsoft.com> wrote in message
> news:0A44BD42-C1EB-45E0-990D-A329D0EBEE1D@microsoft.com...
> > Hello All,
> >
> > I am getting an error any time I try to adjust my Data Source (ODBC)
> settings.
> > Actually I am unable to open any of the DSN connections under User DSN and
> > System DSN.
> >
> > Whenever I try I get this error" The setup routines for the Microsoft
> Access
> > Driver (*.mdb) ODBC driver could not be found. Please reinstall the
> driver."
> >
> > Upon clicking ok that error is quickly followed by "Component not found in
> > registry".
> >
> > How do I reinstall these drivers?
> > And how did I screw up so badly to begin with?
> >
> > I have this error with every ODBC entry I have on this system.
> >
> > Any assistance would be greatly appreciated.
> >
> > Andre
> >
>
> Either the MDAC is hosed or some Administrative permissions have been
> changed. (A Registry corruption is not entirely impossible.)
>
> Has it ever worked?
> What has recently changed?
>
> -ralph
>
>
>

"Andre Gibson" <AndreGib***@discussions.microsoft.com> wrote in message
news:1CC5EC87-6105-4E4A-9317-83A7998B5C90@microsoft.com...
> Yes it all used to work but now whenever I try I get the 2 error I spoke
of
> in my first post.
>
> How can I determine if it is my registry thats corrupted? And if so how
can
> I fix it short of Formatting?
>
> dre
>
> "Ralph" wrote:
>

"Ralph" wrote:

>
> "Andre Gibson" <AndreGib***@discussions.microsoft.com> wrote in message
> news:1CC5EC87-6105-4E4A-9317-83A7998B5C90@microsoft.com...
> > Yes it all used to work but now whenever I try I get the 2 error I spoke
> of
> > in my first post.
> >
> > How can I determine if it is my registry thats corrupted? And if so how
> can
> > I fix it short of Formatting?
> >
> > dre
> >
> > "Ralph" wrote:
> >
>
> I just threw that out - rare but happens. There are various Registry
> Cleaners out there. You likely already have one - RegClean.
>
> First before looking for the exotic, I would re-install the MDAC - it is
> simple to do and likely will repair any 'registry' problems, user access,
> etc. At least then you know the drivers are there. (Also reinstall the Jet
> package).
>
> I would keep googling as there may be a specific published cause. Whenever
> it happened to me, it was because of a faulty install of the MDAC (not all
> users, admin only, etc..)
>
> I honestly suspect it is a permissions problem. But where and how?
> Maybe you are 'locked' out of the Program files\common folder? etc...
>
> You can't rule out any security patches. You can open the CPLApplet for
> "Add/Remove Programs" and get the KB number for any recent installs and then
> google for reported problems. Another way is to open up explorer and in the
> Windows/WinNt folder you will see each patch as a folder. The last part of
> the folder name is the KB#. Also easier to determine dates (when installed).
>
> Be comforted by the fact that when you find the problem it will be a simple
> repair - a setting here, a click there, - so don't go off tearing everything
> up. <g>
>
> -sorry I can't help more.
> -ralph
>
>
>
>
>

"Andre Gibson" <AndreGib***@discussions.microsoft.com> wrote in message
news:CD0F131D-B6A8-4268-B003-0BCD16BA395D@microsoft.com...
> Hey Ralph,
>
> Thanks so much. That was exactly what I needed. I ran the regclean then
> reinstalled mdac, jet4.0, SQL Server and AS400. Worked like a charm.
>
> Thank you.
>
> "Ralph" wrote:
>
> >
> > "Andre Gibson" <AndreGib***@discussions.microsoft.com> wrote in message
> > news:1CC5EC87-6105-4E4A-9317-83A7998B5C90@microsoft.com...
> > > Yes it all used to work but now whenever I try I get the 2 error I
spoke
> > of
> > > in my first post.
> > >
> > > How can I determine if it is my registry thats corrupted? And if so
how
> > can
> > > I fix it short of Formatting?
> > >
> > > dre
> > >
> > > "Ralph" wrote:
> > >
> >
> > I just threw that out - rare but happens. There are various Registry
> > Cleaners out there. You likely already have one - RegClean.
> >
> > First before looking for the exotic, I would re-install the MDAC - it is
> > simple to do and likely will repair any 'registry' problems, user
access,
> > etc. At least then you know the drivers are there. (Also reinstall the
Jet
> > package).
> >
> > I would keep googling as there may be a specific published cause.
Whenever
> > it happened to me, it was because of a faulty install of the MDAC (not
all
> > users, admin only, etc..)
> >
> > I honestly suspect it is a permissions problem. But where and how?
> > Maybe you are 'locked' out of the Program files\common folder? etc...
> >
> > You can't rule out any security patches. You can open the CPLApplet for
> > "Add/Remove Programs" and get the KB number for any recent installs and
then
> > google for reported problems. Another way is to open up explorer and in
the
> > Windows/WinNt folder you will see each patch as a folder. The last part
of
> > the folder name is the KB#. Also easier to determine dates (when
installed).
> >
> > Be comforted by the fact that when you find the problem it will be a
simple
> > repair - a setting here, a click there, - so don't go off tearing
everything
> > up. <g>
> >
> > -sorry I can't help more.
> > -ralph
> >

"Ralph" wrote:

>
> "Andre Gibson" <AndreGib***@discussions.microsoft.com> wrote in message
> news:0A44BD42-C1EB-45E0-990D-A329D0EBEE1D@microsoft.com...
> > Hello All,
> >
> > I am getting an error any time I try to adjust my Data Source (ODBC)
> settings.
> > Actually I am unable to open any of the DSN connections under User DSN and
> > System DSN.
> >
> > Whenever I try I get this error" The setup routines for the Microsoft
> Access
> > Driver (*.mdb) ODBC driver could not be found. Please reinstall the
> driver."
> >
> > Upon clicking ok that error is quickly followed by "Component not found in
> > registry".
> >
> > How do I reinstall these drivers?
> > And how did I screw up so badly to begin with?
> >
> > I have this error with every ODBC entry I have on this system.
> >
> > Any assistance would be greatly appreciated.
> >
> > Andre
> >
>
> Either the MDAC is hosed or some Administrative permissions have been
> changed. (A Registry corruption is not entirely impossible.)
>
> Has it ever worked?
> What has recently changed?
>
> -ralph
>
>
>

"Paul Clement" wrote:

> On Wed, 21 Sep 2005 12:24:03 -0700, Andre Gibson <AndreGib***@discussions.microsoft.com> wrote:
>
> ¤ Hello All,
> ¤
> ¤ I am getting an error any time I try to adjust my Data Source (ODBC) settings.
> ¤ Actually I am unable to open any of the DSN connections under User DSN and
> ¤ System DSN.
> ¤
> ¤ Whenever I try I get this error" The setup routines for the Microsoft Access
> ¤ Driver (*.mdb) ODBC driver could not be found. Please reinstall the driver."
> ¤
> ¤ Upon clicking ok that error is quickly followed by "Component not found in
> ¤ registry".
> ¤
> ¤ How do I reinstall these drivers?
> ¤ And how did I screw up so badly to begin with?
> ¤
> ¤ I have this error with every ODBC entry I have on this system.
> ¤
> ¤ Any assistance would be greatly appreciated.
>
> Which version of Windows are you using?
>
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)
>