MDAC 2.5 SDK - OLE DB Providers
State into what application or system architecture, or what scenario, this provider fits. What are the other system and application components?
What software application problem does it solve? Describe all scenarios.
[If applicable, include architectural diagram(s).]
The following technical articles and white papers are posted on the "Technical Materials" page of the Universal Data Access Web site at http://www.microsoft.com/data/techmat.htm, or included with the Microsoft® Data Access Components (MDAC) SDK. Articles are listed here in order of their relevance.
Their presence and location are subject to change with each release. Other articles can be found in the Microsoft Developer Network (MSDN) Library. Detailed articles concerning known limitations or workarounds can be found in the MSDN Knowledge Base.
| Documents | Date written/posted |
References
ADO Programmer's Reference
Web sites
http://www.microsoft.com/data/oledb
http://www.microsoft.com/data/ado
Optional introduction of new features.
Brief introduction to explain how you can make this provider work.
If applicable, what tools are required (or helpful) to customize the provider, and how are they used? This might include testing/debugging tools, provider construction tools, or provider templates.
Include samples in applicable languages.
Describe how to call the provider in typical scenarios. Some providers are designed to work with other providers; some providers can work alone.
Show samples.
List and describe the OLE DB, COM, and/or ADO interfaces that this provider supports.
Descriptions might be minimal if the interfaces are similar to the interfaces in the relevant Programmer’s Reference.
Insert snippets of code here or reference the “Samples” section if necessary.
List and describe the OLE DB, COM, and/or ADO properties that this provider supports.
Descriptions might be minimal if the properties are similar to the properties in the relevant Programmer’s Reference.
| Property | Description |
| prop 1 | desc |
| prop 2 | desc |
If the provider exhibits specific behaviors, then introduce here. Answer the question: What makes specific behaviors necessary? What are the limitations and caveats of this provider?
Include code (snippets would be adequate) where beneficial.
specific behavior
specific behavior
Text is optional. At most, describe briefly.
File name(s) or installation sources
Required products
Version compatibility
Product compatibility and dependencies
Add topics as necessary.