Hi,

I cannot think of a way without creating many problems . If you need to
search for
.dll files, the ideal command to use is Dir. A good example is in the MSDN
library
which should be included in your distribution.

A work around would be to include your oledb32.dll file in your distribution
when you
set your install programme.

Hoping this will help,

Richard Wang


----- Original Message -----
From: Philip.Ware <Philip.Ware@e...>
To: professional vb <pro_vb@p...>
Sent: Thursday, June 01, 2000 12:35 PM
Subject: [pro_vb] Re: ADO Connection provider


> Thanks for your replys, very helpfull - I wish I knew about this mailing
> list a year ago! :)
>
> Yes - the problem is basically I have installed the wrong MDAC_typ on the
> clients machine.
> and my code specifies the version number, 3.51.  e.g.
>
> ADOConnection.Provider = "Microsoft.JET.OLEDB.3.51"
>
> However, he has 4.0 - and so my code correctly reports, cant find ADO
> provider.
>
> My solution to my installation head ache is to revert back to using ODBC
and
> just use the
> "Microsoft Access Driver (*.mdb)"
> This way - no matter what version is installed it will run.
>
> I have found that this has slowed down my program, and would like to
bypass
> ODBC!
>
> How can I, in VB, search for the installed JET version and then pick that
> version number. e.g.
>
> Provider_version = Get_JET_OLEDB_Version()
> SELECT CASE Provider_version
> CASE 3.51
> ADOConnection.Provider = "Microsoft.JET.OLEDB.3.51"
> CASE 4.0
> ADOConnection.Provider = "Microsoft.JET.OLEDB.4.0"
> END SELECT
>
> ADOConnection.ConnectionString = "blar blar"
> ADOConnection.Open
>
>
> Any comments?
>
> Thanks for your help,
> Philip Ware.
>