B
Ben
Hi all -
In DAO, there's a currentdb object, is there a similar ADO equivalent?
Thanks,
Ben
--
In DAO, there's a currentdb object, is there a similar ADO equivalent?
Thanks,
Ben
--
Not really, but maybe CurrentProject is sufficent for you.In DAO, there's a currentdb object, is there a similar ADO equivalent?
Just curious. If you're familiar with DAO, why are you switching
to ADO? Hopefully it's not because someone told you should because
ADO is replacing DAO, because that's simply not true.
Some Jet 4.0 extensions are (at least, were) only available
through ADO.
The
powerful CHECK( ) constraint (as defined by Jet, not the standard
one, limited ) among one of them, as example. Sure, once it is
defined, it fires even if you then use DAO or ADO since the
database engine will simply see the constraint (and not WHAT
append it to the db).
I didn't mentioned late binding.
introduce artificial hurdles to continuing to use DAO in order to
They maintained their old code with minimal changes. That was a
reasonable approach, that every software developer should emulate.
So people had a choice, use the old backward compatible object,
that wasn't broken very much, or the new forward compatible
object, that, like lots of new software, promised more than it
delivered.
Choices are good.
Maintaining the old code instead of breaking it is good.
The problem was that ADO wasn't good enough to convince the
user base to switch.
But the fact is that there was never a coherent argument presented
for switching from DAO to ADO.
The argument which was presented
was for switching from ODBC-API to a DAO-like COM object.
And if they couldn't present a coherent argument to the users, one
suspects that no coherent argument was made internally.
suspects that no coherent argument was made internally.
Michel Walsh said:... But now, even ADO.Net is losing favor for other mechanics allowing a
better 'compatibility match' between class-oriented technology
(hierarchy), technology used by the code, and databases (relational),
technology supporting the data. Such a match in action is LINQ (even
allowing SQL- like data retrieval to data which can be stored, as example,
in an array rather than in "database" ) and whatever can come next.
Vanderghast, Access MVP
Is it necessary an exclusive or?