Not sure whether this belongs in the W2K group or the Access group. I'll
try here first.

I'm developing an application which must run on W2K and must create an
MS Access database, without a copy of MS Access being installed.

The good news is that W2K installs complete with some ADO drivers for MS
Access. I can create an Access database and use SQL statements to create
some tables therein.

The bad news is that I can only get Jet.OLEDB.4.0 to work. I can't seem
to get Jet.OLEDB.3.51 to work. Which means that I can't create the MS
Access 97 format.

This leaves me with a few questions:

1/ Does this mean that W2K doesn't have the 3.51 Jet ADO drivers?

2/ I understand that I can download the drivers from the MS website.
What are the copyright/licence implications of distributing the drivers
with my application?

3/ How do I find out what ADO drivers are installed?

4/ Some topic drift here... which Jet ADO drivers are supplied with
Windows XP?

Thanks in advance for any info.
--
Simon Elliott
http://www.ctsn.co.uk/

The MS 'Component checker' tool, gives much info
http://msdn.microsoft.com/library/de...dataaccess.asp
Must confess I thought Jet was backward compatible, I use A97 and A2K with
Jet4
Frm recollections there are implications in trying to use ADO and A97
If you do/have done a Win2K update the Jet will have been updated frm
origonal, if you selected to do so.
There was a recent Jet update for WinXP, 4.?
Surely you've covered Licence implications during the development of
Firestat?
David


"Simon Elliott" <(E-Mail Removed)> wrote in message
newsz+PZFAjq34$(E-Mail Removed)...
> Not sure whether this belongs in the W2K group or the Access group. I'll
> try here first.
>
> I'm developing an application which must run on W2K and must create an
> MS Access database, without a copy of MS Access being installed.
>
> The good news is that W2K installs complete with some ADO drivers for MS
> Access. I can create an Access database and use SQL statements to create
> some tables therein.
>
> The bad news is that I can only get Jet.OLEDB.4.0 to work. I can't seem
> to get Jet.OLEDB.3.51 to work. Which means that I can't create the MS
> Access 97 format.
>
> This leaves me with a few questions:
>
> 1/ Does this mean that W2K doesn't have the 3.51 Jet ADO drivers?
>
> 2/ I understand that I can download the drivers from the MS website.
> What are the copyright/licence implications of distributing the drivers
> with my application?
>
> 3/ How do I find out what ADO drivers are installed?
>
> 4/ Some topic drift here... which Jet ADO drivers are supplied with
> Windows XP?
>
> Thanks in advance for any info.
> --
> Simon Elliott
> http://www.ctsn.co.uk/
>
>
>
>
>
>

DL <(E-Mail Removed)> writes
>The MS 'Component checker' tool, gives much info
>http://msdn.microsoft.com/library/de...dataaccess.asp

Thanks for this.

>Must confess I thought Jet was backward compatible, I use A97 and A2K with
>Jet4
>Frm recollections there are implications in trying to use ADO and A97

You can work with an existing A97 database using Jet.OLEDB.4.0. But you
can't create a new A97 database.

>If you do/have done a Win2K update the Jet will have been updated frm
>origonal, if you selected to do so.
>There was a recent Jet update for WinXP, 4.?
>Surely you've covered Licence implications during the development of
>Firestat?

Firestat was a VB application which relied on the VB runtime. Although
it worked well, the VB runtime caused a number of problems. It was very
large, sometimes components would not register on customers' PCs, and if
the customer already had an application written with a different version
of VB, DLL hell could result.

If I were to develop this application again, I'd probably use C++ and
ADO, and deliver a monolithic executable which wouldn't need a complex
installation procedure, and which would be much smaller than the VB
runtime.
--
Simon Elliott
http://www.ctsn.co.uk/

From distant memory I recollect that there are serious implications in
trying to use ADO and A97
Fraid I dont remember precise details but I believe you cannot
David

"Simon Elliott" <(E-Mail Removed)> wrote in message
news:xEm5UDAHyA5$(E-Mail Removed)...
> DL <(E-Mail Removed)> writes
> >The MS 'Component checker' tool, gives much info
>
>http://msdn.microsoft.com/library/de...list/dataacces
s.asp
>
> Thanks for this.
>
> >Must confess I thought Jet was backward compatible, I use A97 and A2K
with
> >Jet4
> >Frm recollections there are implications in trying to use ADO and A97
>
> You can work with an existing A97 database using Jet.OLEDB.4.0. But you
> can't create a new A97 database.
>
> >If you do/have done a Win2K update the Jet will have been updated frm
> >origonal, if you selected to do so.
> >There was a recent Jet update for WinXP, 4.?
> >Surely you've covered Licence implications during the development of
> >Firestat?
>
> Firestat was a VB application which relied on the VB runtime. Although
> it worked well, the VB runtime caused a number of problems. It was very
> large, sometimes components would not register on customers' PCs, and if
> the customer already had an application written with a different version
> of VB, DLL hell could result.
>
> If I were to develop this application again, I'd probably use C++ and
> ADO, and deliver a monolithic executable which wouldn't need a complex
> installation procedure, and which would be much smaller than the VB
> runtime.
> --
> Simon Elliott
> http://www.ctsn.co.uk/
>
>
>
>
>
>