Randy Harris wrote:
On Mon, 30 Oct 2006 15:05:57 -0600, "David W. Fenton"
<XX*******@dfenton.com.invalidwrote:
The question makes no sense. If you're working with Jet data, you
shouldn't be using ADO.
I guess I have no sense. I'm just not smart enough to realize that I
shouldn't be using ADO.
Me too! David has told us often enough. Why can't we learn?
Lyle Fairfield
from
http://msdn.microsoft.com/library/de...dacroadmap.asp
Current MDAC Components
These components are supported in the current release. Use these
components when you develop new applications or upgrade existing
applications.
ADO: ActiveX Data Objects (ADO) provides a high-level programming model
that will continue to be enhanced. Although a little less performant
than coding to OLE DB or ODBC directly, ADO is straightforward to learn
and use, and can be used from script languages such as Microsoft Visual
Basic® Scripting Edition (VBScript) or Microsoft JScript®.
--------------
Obsolete Data Access Technologies
Obsolete technologies are technologies that have not been enhanced or
updated in several product releases and that will be excluded from
future product releases. Do not use these technologies when you write
new applications. When you modify existing applications that are
written using these technologies, consider migrating those applications
to ADO.NET.
The following components are considered obsolete:
....
Data Access Objects (DAO): DAO provides access to JET (Access)
databases. This API can be used from Microsoft Visual Basic®,
Microsoft Visual C++®, and scripting languages. It was included with
Microsoft Office 2000 and Office XP. DAO 3.6 is the final version of
this technology. It will not be available on the 64-bit Windows
operating system.
.....
