DAO / ADO

=?Utf-8?B?Um9kIFBsYXN0b3c=?=
wrote in :

"David W. Fenton" wrote:

=?Utf-8?B?Um9kIFBsYXN0b3c=?=
wrote in
:

I suggest you look at the publication date of those books.
That advice had me converting from DAO to ADO about six years
ago. Now I've had to reconvert.

Many of us saw the folly in using ADO for Jet databases at the
time MS was recommending and didn't convert. I'm not sure why
anyone thought it was a good idea in that environment.

Aye, but it was the threat of withdrawn support that motivated me.


I don't recally any such threat. There were, of course, all those
comments by non-MS employees about Jet being obsolete and deprecated
and all that, but I never believed any of it, as I couldn't see what
could possibly replace Jet (and based on Access 2007 and the ACE, MS
seems to agree with me on that).

Was it
more than 6 years ago?

Absolutely. And it's been a very long time now since MS changed
their tune and started making sense again.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

"David W. Fenton" wrote:

I suggest you look at the publication date of those books. That
advice had me converting from DAO to ADO about six years ago. Now
I've had to reconvert.

Many of us saw the folly in using ADO for Jet databases at the time
MS was recommending and didn't convert.

Many of us, ok me, were too lazy to be bothered to convert from DAO to
ADO. smile

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/