[permalink] [id link]
* MDAC 1. 5b: came with Windows NT 4. 0 Option Pack & Office 97
from
Wikipedia
Some Related Sentences
MDAC and 1
; MDAC 1. 0
MDAC 1. 0 was first released in August 1996.
According to Microsoft, " MDAC 1. 0 existed more as concept than a coordinated, stand-alone setup program.
" The MDAC 1. 0 stack consisted of ODBC 3. 0, OLE DB 1. 1, ADO 1. 0, and the Advanced Data Connector ( ADC ) 1. 0 — which according to Microsoft was the precursor to the Remote Data Service of MDAC 1. 5.
MDAC 1. 0 was released via several mechanisms: the Advanced Data Connector shipped with Internet Information Server ( IIS ) 3. 0 and as a downloadable cab file ; OLE DB 1. 1 and ADO 1. 0 shipped with the OLE DB 1. 1 SDK, which came with Visual Studio 97 and was also downloadable.
MDAC 1. 0 came with Active Server Pages, that itself came in IIS 3. 0, and also came with Visual InterDev 1. 0.
; MDAC 1. 5
MDAC 1. 5 was released between September 1997 and March 1998, and involved a more centralised distribution mechanism than MDAC 1. 0.
MDAC and .
This bridge forms part of the MDAC system component bundle, together with other database drivers.
OLE DB is part of the Microsoft Data Access Components ( MDAC ) stack.
Microsoft Data Access Components ( commonly abbreviated MDAC ; also known as Windows DAC ) is a framework of interrelated Microsoft technologies that allows programmers a uniform and comprehensive way of developing applications that can access almost any data store.
The first version of MDAC was released in August 1996.
At that time Microsoft stated MDAC was more a concept than a stand-alone program and had no widespread distribution method.
Later Microsoft released upgrades to MDAC as web-based redistributable packages.
Eventually, later versions were integrated with Microsoft Windows and Internet Explorer, and in MDAC 2. 8 SP1 they ceased offering MDAC as a redistributable package.
Throughout its history MDAC has been the subject of several security flaws, which led to attacks such as an escalated privileges attack, although the vulnerabilities were generally fixed in later versions and fairly promptly.
MDAC is now known as Windows DAC in Windows Vista.
The latest version of MDAC ( 2. 8 ) consists of several interacting components, all of which are Windows specific except for ODBC ( which is available on several platforms ).
MDAC architecture may be viewed as three layers: a programming interface layer, consisting of ADO and ADO. NET, a database access layer developed by database vendors such as Oracle and Microsoft ( OLE DB,. NET managed providers and ODBC drivers ), and the database itself.
These component layers are all made available to applications through the MDAC API.
The Microsoft SQL Server Network Library, a proprietary access method specific to Microsoft SQL Server, is also included in the MDAC.
Developers of Windows applications are encouraged to use ADO or ADO. NET for data access, the benefit being that users of the application program are not constrained in their choice of database architecture except that it should be supported by MDAC.
Though Net-Lib is specific to the SQL Server, Microsoft includes it with MDAC.
The Banyan VINES, AppleTalk, ServerNet, IPX / SPX, Giganet, and RPC Net-Libs were dropped from MDAC 2. 5 onwards.
OLE DB ( also called OLEDB or OLE-DB ) allows MDAC applications access to different types of () stores in a uniform manner.
OLE DB is the database access interface technology used by MDAC.
MDAC and came
It only came with the ADO / MDAC runtime components.
* MDAC 1. 5d: came included with Windows 98 and Internet Explorer 4. 01 service pack 1.
MDAC and with
With the popular adoption of Transact-SQL, which extends SQL with such programming constructs as loops and conditional statements, this became less necessary and it was eventually deprecated in MDAC 2. 7.
SQLXML was designed for SQL Server 2000, but was deprecated with MDAC 2. 6.
* MDAC 1. 5 ( initial release ): included with Internet Explorer 4. 0 and the Internet Client SDK.
* MDAC 1. 5c: fixed issues with ADO threading and ODBC Connection Pooling and was distributed via the Microsoft website.
MDAC 2. 0 was distributed with the Data Access 2. 0 SDK and included the contents of MDAC 1. 5, the ODBC 3. 5 SDK and the OLE DB 1. 5 SDK, and the OLE DB for OLAP Specification.
MDAC 2. 1 was distributed with SQL Server 7. 0 and SQL Server 6. 5 SP5.
MDAC 2. 1 SP1 was distributed with Internet Explorer 5 and MDAC 2. 1 SP1a ( GA ) was distributed with Microsoft Office 2000, BackOffice 4. 5 and Visual Studio 98 SP3.
MDAC 2. 5 was released on February 17, 2000 and distributed with Windows 2000, and the MDAC service packs were released in parallel with the Windows 2000 service packs.
MDAC and Windows
Jet is now part of Microsoft Windows and is no longer a component of Microsoft Data Access Components ( MDAC ).
According to Microsoft, SQLOLEDB will be " the primary focus of future MDAC feature enhancements will be available on the 64-bit Windows operating system.
MDAC 1. 5 was the last data access component release supported under Windows NT 3. 51 SP5.
Microsoft also discovered a problem in Windows 95, Windows 98, and Windows Me's setup program which prevented the MDAC installation program from rolling back when it encountered an installation error.
MDAC 2. 8 was released in August 2003 and distributed with Microsoft Windows Server 2003, as well as on Microsoft's Data Access Technologies website.
Windows 7 SP1 has broken backwards compatibility of MDAC 2. 8.
Software compiled on Windows 7 SP1 that relies on MDAC ADO will not work on Windows versions prior to Windows 7 SP1 ( including Windows 7 RTM, Vista, XP ).
0.122 seconds.