The problem sounds like your version of Access is providing the OLEDB and
ODBC providers, and those providers link with the old MDAC. This is pretty
odd, because installing MDAC should give you new providers.
I suppose this could happen if you have Access in memory when you updated
the MDAC components, and since the old providers are all COM based, they
would find the memory version first. That's just a guess.
Does this still happen after you reboot?
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Robert W." <Ro*****@discussions.microsoft.com> wrote in message
news:74**********************************@microsof t.com...
I'm trying to add simple database functionality with a Windows Forms app
I'm
building. FYI my development machine is running Windows XP Pro, with all
the
service packs installed.
First I tried using the standard OLEDB connection string (ie.
"Provider=Microsoft.Jet.OLEDB.4.0...") but got this message when it tried
to
open the connection:
"The .Net Data OLE DB Provider(System.DAta.OleDb) requires Microsft Data
Access Component(MDAC) version 2.6 or later. Version 2.51.5303.0 was
found
currently installed."
I was shocked at this but went to the trouble to ensure that indeed I did
have the latest MDAC (2.8) installed.
So how come I'm getting this message?
P.S. The same message came up when I tried instead to connect via ODBC.
Robert W.
--
Robert W.
Vancouver, BC
www.mwtech.com