Problem installing a database app on client PC (NT), it seems that if I use
the "Provider=Microsoft.Jet.OLEDB.3.51;" for a ADODB recordset or the
DataEnvironment I have problems.

For example when I try to open the database (with Provider=Microsoft.Jet.OLEDB.3.51)
I get the follwing error:
"Provider cannot be found. It may not be properly installed."

but if I use the following, I am OK.
"Provider=MSDASQL.1;Persist Security Info=False;Driver={Microsoft Access
Driver (*.mdb)};DriverId=281;FIL=MS Access;MaxBufferSize=2048;MaxScanRows=8;PageTimeout=5;SafeTransactions=0;Threads=3;UID=adm in;UserCommitSync=Yes;FILEDSN="

I do not know what could be the problem, I was able to get around the
problem with ADODB.Recordset by switching to the "Provider=MSDASQL.1;"

But I have a big problem with the DataEnvironment, I have created about
20 reports that use parameters and the reports work fine when using the
Microsoft.Jet.OLEDB.3.51 provider, but if try to switch to the "Provider=MSDASQL.1;"
I get a run time error (Parameter Type not supported), I
guess the MSDASQL.1 provider does not allow parameters to be used. This is
not
acceptable. So I must be able to somehow force the Microsoft.Jet.OLEDB.3.51
driver
to be loaded on to the NT system. May be I must accept the fact that the
app can not
run on NT using the (Provider=Microsoft.Jet.OLEDB.3.51).

Does any one have any Ideas on this subject, or better still has any one
documented the
steps needed to insure that an app built on a development system will install
and run on
a client system?