Distributing VB.NET application with ADO accessing Jet 4.0

Distributing VB.NET application with ADO accessing Jet 4.0

Post by Marcin Flo » Mon, 08 Dec 2003 21:25:06


Hello!

I am writing and application which uses ADO to connect to
Microsoft Access 2000 database (a .mdb file) using
Microsoft.Jet.OLEDB.4.0 provider. I wish to distribute
this application later on. I would like to make sure this
application will work propperly even if the end user has
Windows 98 / NT 4.0 (2000/XP as well) installed and does
not have Microsoft Office installed (or has Microsof
Office 97 or earlier). What componnent should I add with
the installer. Is MDAC necessary? I know ADO.NET requires
MDAC 2.7 or later but is it the same with ADO. Do I have
to redistribute JET 4.0 or will it be contained (by
dafault) in my distribution. Any hints I would
appreciate, thanks for help!

PS. I want to use .NET deployment scheme

Marcin Floryan
marcin(at)floryan(dot)neostrada(dot)pl
 
 
 

Distributing VB.NET application with ADO accessing Jet 4.0

Post by Marcin Flo » Tue, 09 Dec 2003 00:48:44


Utkownik "Val Mazur" < XXXX@XXXXX.COM > napisaw wiadomoi

>> By-default JET will not be included into your installation and Jet is not
a >> part of MDAC starting MDAC 2.6. You would need to include it separately or >> install it separately. Jet installation comes separately and you could >> download latest version of it from the next link, but when you check it,
you >> will see that Jet installation is Windows-specific. It add some complexity >> to the distribution of the application, since, depending on the version of >> Windows installed on client's PC, you would need to use different >> installation of Jet. In this case I would suggest not to include Jet into >> your package and install it separately or notify client they need to
install >> Jet separately themselves

Thank you very much, I just have had the files downloaded (for every
paltform I need).
Yet I would like to make sure - this SP8 is a full installation and does not
need any previous versions, yes?
Because I thought I read somewhere that this is just an upgrade and requires
that Jet 4.0 is already installed,
but looking again - I can see it should be fine even if there is no previous
installation of office or so.

Then, may I ask yet another question - is there a way to check (during the
installation) if Jet 4.0 is already installed
(in other words where to look for it?)

Thank you very much for your help!

 
 
 

Distributing VB.NET application with ADO accessing Jet 4.0

Post by Roy Soltof » Wed, 10 Dec 2003 00:22:51

This link gives you info about how to determine the levelof Jet 4.0
installed:

http://www.yqcomputer.com/ ;en-us;239114



>> >>>> By-default JET will not be included into your installation and Jet is
not >> a >>>> part of MDAC starting MDAC 2.6. You would need to include it separately
or >>>> install it separately. Jet installation comes separately and you could >>>> download latest version of it from the next link, but when you check it, >> you >>>> will see that Jet installation is Windows-specific. It add some
complexity >>>> to the distribution of the application, since, depending on the version
of >>>> Windows installed on client's PC, you would need to use different >>>> installation of Jet. In this case I would suggest not to include Jet
into >>>> your package and install it separately or notify client they need to >> install >>>> Jet separately themselves >> >> Thank you very much, I just have had the files downloaded (for every >> paltform I need). >> Yet I would like to make sure - this SP8 is a full installation and does
not >> need any previous versions, yes? >> Because I thought I read somewhere that this is just an upgrade and
requires >> that Jet 4.0 is already installed, >> but looking again - I can see it should be fine even if there is no
previous >> installation of office or so. >> >> Then, may I ask yet another question - is there a way to check (during the >> installation) if Jet 4.0 is already installed >> (in other words where to look for it?) >> >> Thank you very much for your help! >> >>