The ADO libraries improved in features and needed bug fixes thefastest. While ADO itselfis essentially non-system dependent, OLE is totally system dependent,and OLE DB was product dependent as well as having a foot in both ADOand OLE.It would take too long to document all the various changes to theMDAC package in its migration from a 'universal' store house to a'specific' ADO/OLE tool, and such information isreadily available on the web, but to highlight a few. Or perhaps it was mostly marketing and MS neverreally expected it to be all that Universal in the first place.One problem was the ADO data access libraries, the second was theimprovement and fixes of the OLE/OLE DB components.
Perhaps too ambitious asproblems appeared almost immediately in trying to keep such a diverseasssortment of tools all current (and provide bug fixes and upgrades)in a single package.
ODBC had gone a long way toproviding this sort of functionality, but ODBC was tied to a singlehierarchical data model - ADO and OLE DB removed this limitation.To implement this grand strategy MS adopted its other rising star -COM - that's where and why OLE is so much a major player.A major point of confusion is that while MDAC releases were/are namedafter the most current version of ADO (the ActiveX Data Objects) theysupported - the MDAC is actually a package of diverse though relatedcomponents - the principle catagories being OLE 'system' support, OLEDB components and OLE DB Providers, and the ADO data access library.(These packages originally also included ISAM and ODBC drivers, andthe DAO data access library, ie - one-stop shopping for all dataaccess.)The strategy was grand and ambitious. Products that shippedwith MDAC, included whatever current version was available and couldbe later updated with subsequent MDAC releases.The MDAC was the keystone of what Microsoft called \"Universal Access\",the idea of a single assortment of tools providing access to any datasource through a single access library.
It hadseparate release cycles from any other product. When ADO was introduced and for most of its history it was supportedby a team separate from the development or system groups.
Pick the version of ADO youwant to use and ignore MDAC.A more detailed and really boring answer follows. The simple answer to the question is yes.
0 kommentar(er)
