Data access object models ________ provides a simpler, higher-level object model than OLE DB and is widely used in database applications for rapid development.

Introduction / Context:
OLE DB is a low-level COM-based data access technology. Many developers prefer a simpler abstraction for rapid application development, scripting, and language interoperability—this is where ADO (ActiveX Data Objects) became popular.

Given Data / Assumptions:

• We compare object models and their complexity.
• We want an easier, higher-level API than OLE DB.
• Targeted at broad language support and quick data tasks.

Concept / Approach:

ADO wraps OLE DB to expose Recordset, Command, and Connection objects that are straightforward to use from VB, VBScript, and other COM-aware languages. It hides much of the provider-specific plumbing while still allowing access to relational and non-relational sources through OLE DB providers.

Step-by-Step Solution:

Verification / Alternative check:

Documentation from Microsoft positions ADO as a high-level interface over OLE DB providers, emphasizing ease of use.

Why Other Options Are Wrong:

• ASP: web framework, not a data API.
• XML: data format, not a data access object model.
• ODBC: procedural C API, not an object model.
• JDBC: Java API, not a generic wrapper over OLE DB.

Common Pitfalls:

• Confusing ADO with ADO.NET (a different .NET-era library).
• Assuming ADO works without OLE DB providers; it relies on them.

Final Answer:

ADO