High-level wrapper over OLE DB In Microsoft’s data access stack, ________ is a convenient cover over OLE DB intended for use by many languages, enabling simpler data access.

Introduction / Context:
OLE DB exposed a powerful but complex COM interface for data access. To make it easier for scripting environments and rapid development tools, Microsoft provided ADO (ActiveX Data Objects) as a high-level wrapper that many languages could use with minimal boilerplate.

Given Data / Assumptions:

• The aim is language-neutral ease of use over OLE DB providers.
• We want an abstraction that hides provider complexity while remaining flexible.
• Interoperability with many languages is a goal.

Concept / Approach:

ADO supplies object abstractions—Connection, Command, Recordset—that map to OLE DB operations via providers. This reduces the need to manage COM interfaces directly, encouraging widespread adoption in classic ASP, VB, and scripting scenarios.

Step-by-Step Solution:

Verification / Alternative check:

Microsoft platform histories describe ADO as the mainstream high-level API over OLE DB prior to .NET-era ADO.NET.

Why Other Options Are Wrong:

• ODBC: different stack; not an OLE DB cover.
• ASP: server pages framework, not a data API.
• JPCD: non-standard distractor.
• DCOM: infrastructure technology, not a data access wrapper.

Common Pitfalls:

• Assuming ADO and ODBC are interchangeable—they are separate ecosystems.
• Confusing classic ADO with ADO.NET (they have different object models).

Final Answer:

ADO