Re: DAO vs ADO

From: Mary Chipman (mchip_at_online.microsoft.com)
Date: 08/16/04


Date: Mon, 16 Aug 2004 18:31:10 -0400

I find it amazing that you've saved all that old stuff. Well, times
sure have changed since then. For one thing, I don't do flame wars any
more and I learned where the shift key is located on the keyboard :-)

ADO will be around for a while, but it's definitely not the way of the
future. If you're looking forward, think "managed code". It basically
boils down to, if Microsoft has a large installed base of customers
out there using a particular technology, then it will continue to be
supported, if not forever, then for a while longer. I don't see VB6
(or even Jet) dying quite as quickly as some have predicted. I
wouldn't necessarily recommend new development in deprecated
technologies, but I wouldn't recommend re-writing something that works
from the ground up either. FWIW, Access isn't a deprecated technology
per se, although certain features may be. They're already planning
v.next in Redmond. Whether that version will support developer
features compatible with or competitive with .NET is anyone's guess at
this point.

--Mary

On Sun, 15 Aug 2004 07:54:55 +0100, "Craig Alexander Morrison"
<reply@newsgroups.com> wrote:

>Mary, I remember you from the CompuServe days. You moved from a card
>carrying member of the lurking public on a thread titled "Use Primary Key?"
>in 1994 do you remember that? I remember your description of that thread as
>"intellectual mud wrestling".
>
>I also admired the following quote, but forgot to mention it at the time:
>
>"oh, i see... since my name is "mary" i must be a female, thus i only do
>rolodexes and recipes and thus could have no conceivable interest in such an
>elevated discussion amongst real, testosterone-laden developers who have
>big, important clients to design for. well, that derogatory remark sort of
>goes with the territory in this thread, so i'm not even going to bother
>defending myself."
>
>I did like that a lot, thankfully it wasn't to me. Good to see you doing so
>well. I do like the use of the Capital Letters. :-)
>
>...enough of the flashback.
>
>Is ADO a dead duck? Is DAO and/or ADO a useful stepping stone to the .NExT
>thing?



Relevant Pages

  • Re: DAO vs ADO
    ... ADO will be around for a while, but it's definitely not the way of the ... wouldn't necessarily recommend new development in deprecated ... Access isn't a deprecated technology ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Selecting Databases
    ... > I want to change my fondemental base from BDE to one another Technology, ... > Which Technology recommended, dbExpress or ADO? ... The BDE is not recommended for new projects now, ... dbExpress is lightweight, ...
    (borland.public.delphi.database.ado)
  • Re: Getting Autoincrement ID in ADO.NET
    ... One of the principle complaints about ADO classic was how it generated DML ... action commands at runtime. ... but using the new technology. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Getting Autoincrement ID in ADO.NET
    ... I am moving to ... ADO, but using the new technology. ... I have found a partial solution using ExecuteScalar. ...
    (microsoft.public.dotnet.framework.adonet)