VB.NET and MDAC+JET

  • Thread starter Thread starter bz
  • Start date Start date
B

bz

Hi,

When writing database program with VB.NET that accesses MDB and XLS file, do
you guys know if I still need to distribute MDAC and JET4 to the client
machine?

Or .NET framework already comes with all those drivers?

Thanks!


--
There is no answer.
There has not been an answer.
There will not be an answer.
That IS the answer!
And I am screwed.
Deadline was due yesterday.

There is no point to life.
THAT IS THE POINT.
And we are screwed.
We will run out of oil soon.
Click to expand...

http://spaces.msn.com/bzDaCat
 
For BZ, the client need in my idea to have a proper license of office.

Jet is free and if you use AdoNet and when you use OleDB, than you don't
need AFAIK nothing more.

Cor
 
So, you are saying that I still need to install MDAC and JET to the client
machine if I want to access MDB and XLS files.



Cor Ligthert said:
For BZ, the client need in my idea to have a proper license of office.

Jet is free and if you use AdoNet and when you use OleDB, than you don't
need AFAIK nothing more.

Cor
Click to expand...
 
Peter,

As far as I know are all the computers where Net can run on already with the
proper MDAC installed.

Cor
 
So, you are saying that I still need to install MDAC and JET to the
client machine if I want to access MDB and XLS files.
Click to expand...

MDAC has been included as a system component since Windows 2000.

However, most users on Windows 98 should (but you may want to write a check
routine) have MDAC installed as well.
 
MDAC has been included as a system component since Windows 2000.

However, most users on Windows 98 should (but you may want to write a
check routine) have MDAC installed as well.
Click to expand...

BTW, MDAC for Windows 2000 is MDAC v2.5. However, .NET requires MDAC v2.6
and recommends v2.7. Thus you may still want to put some MDAC error
handling just in case.

You'll get this error if you run the app on a machine without MDAC:

The .NET Data SQL Provider (System.Data.SqlClient) requires Microsoft Data
_
Access Components (MDAC) version 2.6 or later.
 
And ...

Mdac 2.5 was the last version that had everything included ( Jet oledb ) to
access Access :-)

Since version 2.5 Jet oledb has become a seperate installation

so my recomendation would be ,, ship the jet oledb merge module with your
deployment and you should be safe

regards

Michel Posseth [MCP]
 
Yes , you do need to make sure that it is installed on the target system
before you start your program

regards

Michel posseth [MCP]
 
So, if I am using ADO.NET to open MDB or XLS files, I still need to install
JET4.

Got it. Thanks!



Michel Posseth said:
Yes , you do need to make sure that it is installed on the target system
before you start your program

regards

Michel posseth [MCP]


bz said:
So, I still need to install JET4 to access MDB and XLS files, do I?
Click to expand...
Click to expand...
 
This is where you can find the latest jet oledb drivers ( servicepack 8 )

http://support.microsoft.com/default.aspx/kb/829558


regards

Michel


bz said:
So, if I am using ADO.NET to open MDB or XLS files, I still need to
install JET4.

Got it. Thanks!



Michel Posseth said:
Yes , you do need to make sure that it is installed on the target system
before you start your program

regards

Michel posseth [MCP]


bz said:
So, I still need to install JET4 to access MDB and XLS files, do I?



Peter,

As far as I know are all the computers where Net can run on already
with the proper MDAC installed.

Cor

"bz" <[email protected]> schreef in bericht
So, you are saying that I still need to install MDAC and JET to the
client machine if I want to access MDB and XLS files.



For BZ, the client need in my idea to have a proper license of
office.

Jet is free and if you use AdoNet and when you use OleDB, than you
don't need AFAIK nothing more.

Cor

"bz" <[email protected]> schreef in bericht
Hi,

When writing database program with VB.NET that accesses MDB and XLS
file, do you guys know if I still need to distribute MDAC and JET4
to the client machine?

Or .NET framework already comes with all those drivers?

Thanks!


--
There is no answer.
There has not been an answer.
There will not be an answer.
That IS the answer!
And I am screwed.
Deadline was due yesterday.

There is no point to life.
THAT IS THE POINT.
And we are screwed.
We will run out of oil soon.

http://spaces.msn.com/bzDaCat
Click to expand...
Click to expand...
Click to expand...
 
Back
Top