469,280 Members | 2,180 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,280 developers. It's quick & easy.

Microsoft.Jet.OLEDB.4.0 provider and mdac_type.exe

Hello,

My VB application read and writes data from and to a MS Excel workbook,
using the Microsoft.Jet.OLEDB.4.0 provider. I have installed the MS ActiveX
Data Object 2.0 Library on my computer and everything works fine.

I have created a setup using the Package & Deployment Wizard. I thought,
let's make the setup a bit more up-to-date, so I included the mdac_type.exe
version 2.7.

However, after installing the setup on a different computer (that never had
the MS ActiveX Data Object 2.0 Library installed), the application cannot
open the MS Excel workbookbecause the provider cannot be found.

After a quick investigation on Microsoft's site, if saw that the Microsoft
Jet OLE DB Provider isn't provided in the mdac_type.exe version 2.7, so it's
clear why the application can't read the MS Excel workbook.

So, in the future, do I have to add the 'old' mdac_type.exe version 2.0 to
my setup instead of the most up-to-date version of mdac_type.exe? Of do I
have to change the way of opening Excel workbooks, instead of using the
Microsoft.Jet.OLEDB.4.0 provider?

Who can help me out?

Jul 17 '05 #1
5 18213

"Geert-Pieter Hof" <g.*******@wbmt.tudelft.nl.blablabla> wrote in message
news:bi**********@azure.qinip.net...
Hello,

My VB application read and writes data from and to a MS Excel workbook,
using the Microsoft.Jet.OLEDB.4.0 provider. I have installed the MS ActiveX Data Object 2.0 Library on my computer and everything works fine.

I have created a setup using the Package & Deployment Wizard. I thought,
let's make the setup a bit more up-to-date, so I included the mdac_type.exe version 2.7.


I am assuing this problem only exist on platform other than Windows 2000.

For 95/98/NT in addition to MDAC you also need to include the install of the
MSJet Engine. The latest I think is at
http://www.microsoft.com/downloads/d...632-57f1-4959-
897f-263877c6a11a&displaylang=en

(all one line of course) for Jet40SP7_9xNT.exe

Beste wensen van New York.
Jul 17 '05 #2
> I am assuing this problem only exist on platform other than Windows 2000.

For 95/98/NT in addition to MDAC you also need to include the install of the MSJet Engine. The latest I think is at
http://www.microsoft.com/downloads/d...632-57f1-4959- 897f-263877c6a11a&displaylang=en

(all one line of course) for Jet40SP7_9xNT.exe


Do you happen to know if I have to install the MSJet Engine in addition to
MDAC of can I install the MSJet Engine instead of the MDAC?

Thanks,

Geert-Pieter
Jul 17 '05 #3

"Geert-Pieter Hof" <g.*******@wbmt.tudelft.nl.blablabla> wrote in message
news:bi**********@azure.qinip.net...
Do you happen to know if I have to install the MSJet Engine in addition to
MDAC of can I install the MSJet Engine instead of the MDAC?


You need BOTH if you're on 95/98/NT environment.
Jul 17 '05 #4
Hi there, I had a similar problem but solved it by using madc 2.5, you may
want to try that?
Chris

"Geert-Pieter Hof" <g.*******@wbmt.tudelft.nl.blablabla> wrote in message
news:bi**********@azure.qinip.net...
Hello,

My VB application read and writes data from and to a MS Excel workbook,
using the Microsoft.Jet.OLEDB.4.0 provider. I have installed the MS ActiveX Data Object 2.0 Library on my computer and everything works fine.

I have created a setup using the Package & Deployment Wizard. I thought,
let's make the setup a bit more up-to-date, so I included the mdac_type.exe version 2.7.

However, after installing the setup on a different computer (that never had the MS ActiveX Data Object 2.0 Library installed), the application cannot
open the MS Excel workbookbecause the provider cannot be found.

After a quick investigation on Microsoft's site, if saw that the Microsoft
Jet OLE DB Provider isn't provided in the mdac_type.exe version 2.7, so it's clear why the application can't read the MS Excel workbook.

So, in the future, do I have to add the 'old' mdac_type.exe version 2.0 to
my setup instead of the most up-to-date version of mdac_type.exe? Of do I
have to change the way of opening Excel workbooks, instead of using the
Microsoft.Jet.OLEDB.4.0 provider?

Who can help me out?

Jul 17 '05 #5
G'day All,
Hey that's a question I can answer. :-)
Yes, don't use MDAC 2.7 Chris is right use 2.5 (version number 4.72.3110.0)
The Microsoft Data Access Components 2.5 RTM is the same version of the MDAC
components installed by Windows 2000.
Available here
http://www.microsoft.com/downloads/d...178-94c9-4e7d-
b0b6-a8a94c4eb912&DisplayLang=en
Details of all the MDAC versions is here
http://msdn.microsoft.com/library/de...ist/dataaccess
..asp
You'll find more details on the Inno Setup Web Site
http://www.jrsoftware.org/isinfo.php
The Inno setup newsgroup is also an excellent source of info, the man with
the best VB answers is Michael Reitz.
hth
build

"Chris & Kathie" <mi*****@ihug.co.nz> wrote in message
news:bj**********@lust.ihug.co.nz...
Hi there, I had a similar problem but solved it by using madc 2.5, you may
want to try that?
Chris

"Geert-Pieter Hof" <g.*******@wbmt.tudelft.nl.blablabla> wrote in message
news:bi**********@azure.qinip.net...
Hello,

My VB application read and writes data from and to a MS Excel workbook,
using the Microsoft.Jet.OLEDB.4.0 provider. I have installed the MS

ActiveX
Data Object 2.0 Library on my computer and everything works fine.

I have created a setup using the Package & Deployment Wizard. I thought,
let's make the setup a bit more up-to-date, so I included the

mdac_type.exe
version 2.7.

However, after installing the setup on a different computer (that never

had
the MS ActiveX Data Object 2.0 Library installed), the application cannot open the MS Excel workbookbecause the provider cannot be found.

After a quick investigation on Microsoft's site, if saw that the Microsoft Jet OLE DB Provider isn't provided in the mdac_type.exe version 2.7, so

it's
clear why the application can't read the MS Excel workbook.

So, in the future, do I have to add the 'old' mdac_type.exe version 2.0 to my setup instead of the most up-to-date version of mdac_type.exe? Of do I have to change the way of opening Excel workbooks, instead of using the
Microsoft.Jet.OLEDB.4.0 provider?

Who can help me out?


Jul 17 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Gianluca_Venezia | last post: by
5 posts views Thread by somersbar | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.