Thanks Lyle, but still unclear on the best route to take. What about ADODB
connection vs. OLEDB?
Thanks again!
<ly******@yahoo.ca> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com...
From ADO 2.8 help:
**** Begin Quote ****
Deprecated Components
Each of the following components is considered obsolete. While these
components are still supported in this release of the Microsoft® Data
Access Components (MDAC), they may be removed in the future. When
writing new applications, you should avoid using these deprecated
components. When modifying existing applications, you are strongly
encouraged to remove any dependency on these components.
ODBC Provider (MSDASQL)
You are strongly encouraged to use one of the native OLE DB Providers
instead of the Microsoft Open Database Connectivity (ODBC) Provider.
Native OLE DB Providers provide better application stability and
performance. Furthermore, native OLE DB Providers will be supported in
the future, whereas MSDASQL will not have any new features added to it,
will not be available on 64-bit, and will not be accessible from the
OLE DB NET Data Provider.
....
Jet and Replication Objects (JRO)
The Microsoft Jet OLE DB Provider and other related components were
removed from MDAC 2.6 and later. Microsoft has deprecated the Microsoft
Jet Engine, and plans no new releases or service packs for this
component. As a result, the Jet and Replication Objects (JRO) is being
deprecated in this release and will not be available in any future MDAC
releases.
**** end quote
Robert Vieira
Professional SQL Server 2000 Programming p. 25
(Wrox)
**** begin quote ****
DAO: Data Access Objects. This is actually native to Microsoft Access
(more specifically, the Jet database that is at the heart of Access).
There are a lot of applications written in VB and Access that use this
technology. Too bad! This object model can be considered clunky, slow,
and just plain outdated (believe me, I'm being nice and not saying what
I really think). It's still the fastest way to access things if you're
using a Jet (Access) database but, if you're using this technology to
access SQL Server, I would suggest putting some serious effort into
migrating away from it as soon as possible. Microsoft was calling DAO a
"legacy" model more than a year before the end of the Office 97
lifecycle. They want people to stop using it, and I have to agree with
them.
**** end quote ****