What does DAO have that ADO/ADOx/JRO do not?

by Michael S. Kaplan, published on 2007/07/13 15:11 +00:00, original URI: http://blogs.msdn.com/michkap/archive/2007/07/13/3849288.aspx

If you don't care about Jet or DAO or Access then this is a post you can skip! 

This post is a reposting of an article written over seven years ago, and is still entirely true.

A few versions ago, the Access team started formally backing away from de-emphasizing DAO and once again was adding it to default references in new databases.

As a culmination of this slow change, the updated version of DAO that is specifically used by Access 2007 and ACE is now once again under active development.

Proof positive that rumors of DAO's (and Jet's) death were greatly exaggerated? :-)

Microsoft has clearly positioned ADO as the replacement to DAO.... many Microsoft representatives have gone to far as to state that DAO is DOA (Dead On Arrival, a term used in the US to describe people who are dead when an ambulance arrives hoping to take them to be saved). HOWEVER a lot of core functionality is supported in DAO that ADO/ADOx/JRO do not support, and might never actually support since Microsoft seems to be pushing customers in other directions. While Jet itself will not "die" it is clear that it is no longer a strategic platform, so there simply does not seem to be enough interest to make things work more effectively in Jet.

Here, for the full record, is a list of all of the capabilities DAO has that ADO does not:


This post sponsored by (U+ff24, a.k.a.FULLWIDTH LATIN CAPITAL LETTER D)

comments not archived

referenced by

2008/09/07 Working hard to make one's work less important

go to newer or older post, or back to index or month or day