Re: Bookmark property works when stepping through code in debug, but not when run
- From: "figaro@xxxxxxxxxx" <figaro@xxxxxxxxxx>
- Date: Wed, 03 Dec 2008 15:02:26 -0800
On 18 Nov 2008 21:56:43 GMT, "David W. Fenton"
<XXXusenet@xxxxxxxxxxxxxxxxxxx> wrote:
"figaro@xxxxxxxxxx" <figaro@xxxxxxxxxx> wrote in
news:klv3i49jenpv1j8c7t61ntrabc8oheqsha@xxxxxxx:
And as to ado.net it seems I'm behind the
times, working as I am from an Access 2002 manual.
ADO.NET is not usable in Access, and probably never will be.
ADO was MS's generic data access interface, introduced into Access
2000 in 1999. MS went on a campaign to try to convince developers to
switch from ADO to DAO, but most developers were smart enough to
realize that for Jet data (and for data accessed via Jet, e.g., all
ODBC data sources), DAO was simply much better than ADO. In the end,
MS realized its mistake and reversed course. ADO is no longer the
preferred data interface, except for certain kinds of operations
with databases via OLEDB interfaces (ADO is a wrapper around OLEDB),
which mostly means SQL Server, and in Access Data Projects (which
work only with SQL Server).
In short, in 2000, there was no real justification for converting
ADO code to DAO, though MS was putting out a lot of propaganda to
make developers think there was some magical benefit to doing so.
In 2008, there is still no justification whatsoever, and it's really
not very wise, given that classic ADO exists only in Access and
classic ASP.
Thanks David for your clear and concise statement of some relevant and
interesting facts!
John
.
- Prev by Date: Combo Box in a Datasheet Form
- Next by Date: RE: Combo Box in a Datasheet Form
- Previous by thread: Combo Box in a Datasheet Form
- Next by thread: runtime Error.. cant assign value to this object
- Index(es):
Relevant Pages
|
