A
Adam
Hey Guys,
I’m trying to create an application that uses an OLEDBConnection.
Every time I try to run my app when I get to the opening of the
connection I get this error.
"The .Net Framework Data Providers require Microsoft Data Access
Components (MDAC). Please install Microsoft Data Access Components
(MDAC) version 2.6 or later."
I have downloaded the latest version of MDAC (2.7) and installed it but
i still get the same error. I downloaded this utility from MS and its
supposed to check which version of MDAC i have installed and it says I
have all of them installed from 2.1 to 2.8 sp1. It doesn’t make any
sense, I have used this type of connection before but i have formatted
since so I’m not sure if there is some little setting that i missed or
if i just got lucky last time. Any input will be greatly appreciated so
thx in advance.
- Adam
P.S.
I am running Windows XP Pro SP2 with Visual Studio .NET 2003 & Visual
Studio .NET 2005 Beta 2. I had the same problem without VS.NET 2005
installed I was kind of hoping that hen I installed VS.NET 2005 it would
fix my problem but it didn’t.
I’m trying to create an application that uses an OLEDBConnection.
Every time I try to run my app when I get to the opening of the
connection I get this error.
"The .Net Framework Data Providers require Microsoft Data Access
Components (MDAC). Please install Microsoft Data Access Components
(MDAC) version 2.6 or later."
I have downloaded the latest version of MDAC (2.7) and installed it but
i still get the same error. I downloaded this utility from MS and its
supposed to check which version of MDAC i have installed and it says I
have all of them installed from 2.1 to 2.8 sp1. It doesn’t make any
sense, I have used this type of connection before but i have formatted
since so I’m not sure if there is some little setting that i missed or
if i just got lucky last time. Any input will be greatly appreciated so
thx in advance.
- Adam
P.S.
I am running Windows XP Pro SP2 with Visual Studio .NET 2003 & Visual
Studio .NET 2005 Beta 2. I had the same problem without VS.NET 2005
installed I was kind of hoping that hen I installed VS.NET 2005 it would
fix my problem but it didn’t.