these are my results
at 1241 record output ADO is 4 sec faster than DAO
at 11635 record output ADO is 17 sec faster than DAO
seriously.. you're fucking deranged MORON!
provide your sql fucker, or are you scared to?
give me a MDB that will compare and contrast, show me your VBA.
and for the record; DAO does take LONGER during development; so it's
pointless because DAO has a negative ROI
and of course, DAO isn't included in Windows or Access.
so it's slower execution, slower development, _HUGE_ risk of memory
leaks.. and of course DAO is a fucking pain in the ass to deploy. DAO
hasn't even been included in MDAC for a few years now buster
and when you lose the fucking training wheels you fucking pansy--
try comparing JET DAO against SQL ADO
I don't think that I've run into a single sql statement in the past
month that takes more than a second in ADO
MDB & ADO is an impractical choice because everyone knows that MDB is
obsolete and worthless.
Lose the training wheels fucknut; I can scan a billion records in SQL
Server with sub-second response times.
It is called Analysis Services, fucknut
when MDB and your piddly little MDB supports their own Olap engine is
when I go back to the 90s and start using DAO
-Aaron
Franck wrote:
aa*********@gma il.com wrote:
you're so fucking full of shit dude
DAO was never faster ONCE than ADO
I tried few query :
at 1241 record output DAO is 4 sec faster than ADO
at 11635 record output DAO is 17 sec faster than ADO
DAO ADO jet.4.0 in access
so your comment doesnt apply to my case, i was always faster than ADO
for me and it's still faster, maybe depend on your opinion that is
wrong and youll keep stick to it because i know you are closed minded