Access | Data Microsoft Data Access component
Microsoft Data Access Components (MDAC) provide an easy-to-use, programmable access to all data throughout the enterprise. Data-driven client/server applications developed on a Web or local area network can use these components to easily combine information from a variety of resources, whether relevant or unrelated. Microsoft Data Access components include ActiveX Data Objects (ADO) and Remote Data Services (RDS), Microsoft OLE DB Vendors for ODBC, Open Database Connectivity (ODBC), and Microsoft SQL Server. Microsoft Access and other desktop databases, as well as improved ODBC drives for Oracle databases. All of these components have been published, documented, and supported.
Microsoft Data Access Components (MDAC) support a variety of different application scenarios. How you use Microsoft Data Access Components (MDAC) depends on the scenario of the application you are developing. The Microsoft Data Access Component (MDAC) supports the following scenarios:
Intranet client/Server
Internet client/server
Microsoft Windows LAN Client/server
Single
Intranet client/Server
When you develop an intranet (after firewall) application through Microsoft Internet Information Server 4.0 (IIS) and Microsoft Internet Explorer 4.0, you can take full advantage of the capabilities and flexibility of ADO and RDS. A large variety of application scenarios are possible:
Use Compiled.dll (written in Microsoft Visual Basic,microsoft Visual C + + or Microsoft Visual J + +) to access data, using Remote Data Services (RDS)
Use Microsoft Visual Basic's ActiveX Data object, Script Editor (VBScript), or iscript to access data on an ASP page, while using Remote Data Services (RDS) to extend data to the client;
Using the default business object--RDSServer.DataFactory connects the remote data (RDS) service directly to the data source. No server-side code is required.
Internet client/server
If your target client is on a non-Windows platform, such as an Internet application that provides data to any browser, you cannot use a remote server (RDS), no matter what platform. However, you can still use ActiveX Data Objects (ADO) to provide data through HTML control. Because arbitrary data manipulation, scrolling, modification, and so on, occur on the server, which leads to more circular access between the client and the server, which slows it down.
Microsoft Windows LAN Client/server
There are many types of intranet scenarios in which windows-based clients use DCOM (the distributed generic object model) to connect to the server instead of the HTTP protocol. Despite the use of the httpintranet scenario, servers and clients can take advantage of ActiveX Data Objects (ADO) and Remote Data Services (RDS). The biggest difference is that a custom client's execution program must be installed on each client computer.
Single
In a stand-alone application, you use the ActiveX Data Object (ADO) interface and an OLE DB data provider with Microsoft Visual Basic,microsoft Visual C + + or Microsoft Visual J + + The language is connected. An ActiveX Data Object (ADO) is a dual Interface Component Object Model (COM) library. So you can think of it as any part of a windows-based application.
