Can not find Microsoft.Jet.OLEDB.4.0

18 May 2009 11:56 PM

moondaddy

I have a vb.net 2.0 app that was being developed on a WinXP 32 bit machine.
I now have a new 64 bit machine, did a clean install of vista 64 bit,
installed sql server 2008 developer edition full install, VS 2008 TS for
database professionals full install, and office Enterprise editions full
install.

the .net app needs top get data from an Access database on the same machine,
but I now get following error when I try to open the command's db
connection:

"The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local
machine."

How can this be?

I downloaded and ran a tool called CompChecker and it found the following
files. Can someone please help resolve this?

Thank you!

--
moondaddy@newsgroup.nospam

[attached file: mdac.png]

19 May 2009 12:15 AM

moondaddy

OK I found an answer which begs another question. First the answer: found
it here
http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/45aa44dd-0e6f-42e5-a9d6-9be5c5c8fcd1
There is not 64 version of Jet so we must tartet the 32 bit version.

Project Properties...Compile tab...Advanced Compile Options button...Target
CPU dropdown.

Now the new question. if I compile the project like this, will it always
work on 64 bit systems in the future?

Thanks.

Show quoteHide quote

"moondaddy" <moondaddy@newsgroup.nospam> wrote in message
news:u1d1mRB2JHA.1864@TK2MSFTNGP02.phx.gbl...
>I have a vb.net 2.0 app that was being developed on a WinXP 32 bit machine.
>I now have a new 64 bit machine, did a clean install of vista 64 bit,
>installed sql server 2008 developer edition full install, VS 2008 TS for
>database professionals full install, and office Enterprise editions full
>install.
>
> the .net app needs top get data from an Access database on the same
> machine, but I now get following error when I try to open the command's db
> connection:
>
> "The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local
> machine."
>
> How can this be?
>
> I downloaded and ran a tool called CompChecker and it found the following
> files. Can someone please help resolve this?
>
> Thank you!
>
>
>
> --
> moondaddy@newsgroup.nospam
>
>

19 May 2009 5:45 AM

Michel Posseth [MCP]

Hello .

As long as MS is willing to support 32 bit apps through the WOW layer wich
is most likely a few new operating systems the case ,
another solution for you would be to ditch Access and move to the next
generation counterpart product ( SQL CE ) then your APP wil run 64 bit

Show quoteHide quote

"moondaddy" <moondaddy@newsgroup.nospam> schreef in bericht
news:%23$Ss2bB2JHA.5728@TK2MSFTNGP03.phx.gbl...
> OK I found an answer which begs another question. First the answer:
> found it here
> http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/45aa44dd-0e6f-42e5-a9d6-9be5c5c8fcd1
> There is not 64 version of Jet so we must tartet the 32 bit version.
>
> Project Properties...Compile tab...Advanced Compile Options
> button...Target CPU dropdown.
>
> Now the new question. if I compile the project like this, will it always
> work on 64 bit systems in the future?
>
> Thanks.
>
>
>
> "moondaddy" <moondaddy@newsgroup.nospam> wrote in message
> news:u1d1mRB2JHA.1864@TK2MSFTNGP02.phx.gbl...
>>I have a vb.net 2.0 app that was being developed on a WinXP 32 bit
>>machine. I now have a new 64 bit machine, did a clean install of vista 64
>>bit, installed sql server 2008 developer edition full install, VS 2008 TS
>>for database professionals full install, and office Enterprise editions
>>full install.
>>
>> the .net app needs top get data from an Access database on the same
>> machine, but I now get following error when I try to open the command's
>> db connection:
>>
>> "The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local
>> machine."
>>
>> How can this be?
>>
>> I downloaded and ran a tool called CompChecker and it found the following
>> files. Can someone please help resolve this?
>>
>> Thank you!
>>
>>
>>
>> --
>> moondaddy@newsgroup.nospam
>>
>>
>
>

19 May 2009 3:06 PM

Cowboy (Gregory A. Beamer)

One cannot say always, but it will be supported for some time.

WOW is not going away any time soon, as there are too many windows bits that
are still 32-bit. once everything is truly 64-bit, you might find this
solution fails, but I would imagine that is many, many years away.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************************************************

Show quoteHide quote

| Think outside the box! |
*************************************************

"moondaddy" <moondaddy@newsgroup.nospam> wrote in message
news:#$Ss2bB2JHA.5728@TK2MSFTNGP03.phx.gbl...
> OK I found an answer which begs another question. First the answer:
> found it here
> http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/45aa44dd-0e6f-42e5-a9d6-9be5c5c8fcd1
> There is not 64 version of Jet so we must tartet the 32 bit version.
>
> Project Properties...Compile tab...Advanced Compile Options
> button...Target CPU dropdown.
>
> Now the new question. if I compile the project like this, will it always
> work on 64 bit systems in the future?
>
> Thanks.
>
>
>
> "moondaddy" <moondaddy@newsgroup.nospam> wrote in message
> news:u1d1mRB2JHA.1864@TK2MSFTNGP02.phx.gbl...
>>I have a vb.net 2.0 app that was being developed on a WinXP 32 bit
>>machine. I now have a new 64 bit machine, did a clean install of vista 64
>>bit, installed sql server 2008 developer edition full install, VS 2008 TS
>>for database professionals full install, and office Enterprise editions
>>full install.
>>
>> the .net app needs top get data from an Access database on the same
>> machine, but I now get following error when I try to open the command's
>> db connection:
>>
>> "The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local
>> machine."
>>
>> How can this be?
>>
>> I downloaded and ran a tool called CompChecker and it found the following
>> files. Can someone please help resolve this?
>>
>> Thank you!
>>
>>
>>
>> --
>> moondaddy@newsgroup.nospam
>>
>>
>
>