Microsoft Data Access Components Windows 10 ((BETTER))

Microsoft Data Access Components (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. Its components include: ActiveX Data Objects (ADO), OLE DB, and Open Database Connectivity (ODBC). There have been several deprecated components as well, such as the Jet Database Engine, MSDASQL (the OLE DB provider for ODBC), and Remote Data Services (RDS). Some components have also become obsolete, such as the former Data Access Objects API and Remote Data Objects.

Microsoft data access components windows 10

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. Naturally, developers still have the choice of writing applications which directly access OLE DB and ODBC.

The Shared Memory Net-Lib, on the other hand, manages connections between multiple instances of SQL Server that exist on one computer. It uses a shared memory area to communicate between the processes. This is inherently secure; there is no need for data encryption between instances of SQL Server that exist on one computer as the operating system does not allow any other process access to the instances' area of shared memory.

OLE DB (also called OLEDB or OLE-DB) allows MDAC applications access to different types of data stores in a uniform manner. Microsoft has used this technology to separate the application from data can store in the website the data store that it needs to access. This was done because different applications need access to different types and sources of data, and do not necessarily need to know how to access technology-specific functionality. The technology is conceptually divided into consumers and providers. The consumers are the applications that need access to the data, and the provider is the software component that exposes an OLE DB interface through the use of the Component Object Model (or COM).

Open Database Connectivity (ODBC) is a native interface that is accessed through a programming language (usually C) that can make calls into a native library. In MDAC this interface is defined as a DLL. A separate module or driver is needed for each database that must be accessed. The functions in the ODBC API are implemented by these DBMS-specific drivers. The driver that Microsoft provides in MDAC is called the SQL Server ODBC Driver (SQLODBC), and (as the name implies) is designed for Microsoft's SQL Server. It supports SQL Server v6.5 and upwards.[3] ODBC allows programs to use SQL requests that will access databases without having to know the proprietary interfaces to the databases. It handles the SQL request and converts it into a request that the individual database system understands. According to Microsoft, "After SQL Server 2012, the ODBC driver will be updated for the most recent server features, including Microsoft Windows Azure SQL Database, and released as the Microsoft ODBC Driver for SQL Server."[4]

ActiveX Data Objects (ADO) is a high-level programming interface to OLE DB. It uses a hierarchical object model to allow applications to programmatically create, retrieve, update and delete data from sources supported by OLE DB. ADO consists of a series of hierarchical COM-based objects and collections, an object that acts as a container of many other objects. A programmer can directly access ADO objects to manipulate data, or can send an SQL query to the database via several ADO mechanisms. ADO is made up of nine objects and four collections.

Jet stands for Joint Engine Technology and was a database engine used for Microsoft Access, Microsoft Exchange Server and Visual Basic. Jet was part of a Relational Database Management System (RDBMS) and offered a single interface that other software could use to access Microsoft databases. Jet also provided support for security, referential integrity, transaction processing, indexing, record and page locking, and data replication. In later versions of Jet, the engine was extended to run SQL queries, store character data in Unicode format, create views, and allowed bi-directional replication with the Microsoft SQL Server. It was superseded by MSDE which was superseded SQL Server Express.

There were three modules to Jet. One was the Native Jet ISAM Driver, a Jet dynamic link library (DLL) that could directly manipulate Microsoft Access database files (MDB), which was a modified form of an Indexed Sequential Access Method (ISAM) database. Another one of the modules were the ISAM Drivers, DLLs that allowed access to ISAM databases, among them being Xbase, Paradox, Btrieve and FoxPro files. The final module was the Data Access Objects (DAO) DLL, DAO allowed programmers access to the Jet engine. It was basically an object-oriented data language used by Access Basic and Visual Basic application developers to access Jet.

The Microsoft OLE DB Provider for ODBC, or MSDASQL, was an OLE DB provider for allowing ActiveX Data Objects access to databases via any ODBC driver. Microsoft supplied several OLE-DB providers (for the Indexing Service, Active Directory, Jet, SQL Server, Oracle (MSDAORA[28])and Internet Publishing), however unless otherwise directed, ADO defaulted to using MSDASQL as the default provider. After MDAC 2.5 both the Oracle ODBC driver and MSDASQL supported Oracle 7 and partially supported Oracle 8i. Features that were not supported were:

This version of MDAC had a security flaw that made it vulnerable to an escalated privileges attack. The vulnerability caused systems that had both IIS and MDAC installed to give an unauthorized web user the ability to execute shell commands on the IIS system as a privileged user. This allowed the attacker to use MDAC to tunnel SQL and other ODBC data requests through the public connection to a private back-end network when on a multi-homed Internet-connected IIS system. It also allowed the user to gain unauthorized access to secured, non-published files on the IIS system[38]

Thanks to Thomas Scheidegger for the tip: Microsoft has released MDAC 2.0,the latest version of its universal data access components for programmersand Web developers. This is another one of those things: If you need this,you'll know it. For more information on MDAC, please visit the MicrosoftUniversal Data Access Web Site. You canalso download the new MDAC directly from the MDAC 2.0 Download page 0 comments Hide comments Comment * Switch to plain text editorMore information about text formats

QuickDOC is an ILL-management system designed to interface with DOCLINE, the National Library of Medicine's (NLM's) ILL system. QuickDOC runs on Windows and has two components: the QDPortal Program and the QuickDOC Program. These components copy ILL requests and store them in a database on the local workstation. QuickDOC tracks all ILL requests and automatically updates DOCLINE statuses. It also stores borrowing and lending library addresses, patron and department information, and patron and library billing records.

MDB Viewer Plus has been written to provide a free, quick and easy way to open, view, edit, filter, sort, import to, export from, modify and search MDB and ACCDB files.This is useful for software developers like myself who use Access databases as a backend database for their bespoke software. MDB Viewer Plus provides a convenient way to view and edit these databases. The table info screen even has the ability to copy the list of field names in a table to the clipboard. A developer can then paste this list into their source code for direct access.

Microsoft is announcing an important interoperability milestone: the release of the Microsoft Drivers for PHP for SQL Server 2.0!! The major highlight of this release is the addition of the PDO_SQLSRV driver, which adds support for PHP Data Objects (PDO). The PHP community has signaled that PDO is the future as it removes data access complexity Read more

MDAC is a Windows program package designed to help users who are building applications using ADO, OLE DB and ODBC. It provides documentation, headers, libraries for various platforms, as well as samples and developer tools. Currently, it no longer receives updates and is mainly used to fix the SQL database access errors on various operating systems.

Sometimes MySQL Query Browser or other software that works with databases does not launch or switch to SQL mode. This means that after installing an automatic Windows update, the system components responsible for accessing Microsoft Data Access Components are damaged or deleted. In particular, it is necessary to mention two modules such as ActiveX Data Object and OLEDB Providers

Starting with Windows XP SP2 and Server 2003, the MDSC components are considered an integral part of the operating system. In the Windows Vista and Server 2008 versions, they are renamed Windows Data Access Components and are no longer distributed as a separate installer. So, the best solution is to reinstall the operating system or restore it from a backup copy before any database access failure occurs. Alternatively, you may download this software package. 041b061a72