C
Chris Mills
Most interesting, thanks. It is true that my interest is Access/Jet, where DAO
vs ADO (I use a top-down order <g>) seems to document a preference for DAO.
Not legacy (though that's a good reason), but because I get the impression
that ADO did not live up to it's replacement expectations.
But my original reason (the subject heading!) was not the merits between them,
but that Access sticks in some default references which might not be used. If
they are used then they are of course. But Access can have problems with ANY
reference falling over (such as needing re-registering) and whether it's
actually used in the code or not. One thing to limit this "DLL Hell", is to
remove unnecessary references!
(that is, I have fixed the mentioned error by re-registering DAO, and ADO and
OLEAutomation were not witnesses to the problem)
I think...perhaps I could have fixed it by removing DAO...
Cheers
Chris
vs ADO (I use a top-down order <g>) seems to document a preference for DAO.
Not legacy (though that's a good reason), but because I get the impression
that ADO did not live up to it's replacement expectations.
But my original reason (the subject heading!) was not the merits between them,
but that Access sticks in some default references which might not be used. If
they are used then they are of course. But Access can have problems with ANY
reference falling over (such as needing re-registering) and whether it's
actually used in the code or not. One thing to limit this "DLL Hell", is to
remove unnecessary references!
(that is, I have fixed the mentioned error by re-registering DAO, and ADO and
OLEAutomation were not witnesses to the problem)
I think...perhaps I could have fixed it by removing DAO...
Cheers
Chris