INFO: No Supported Method to Trace OLE DB API Calls (271649)
The information in this article applies to:
- Microsoft Data Access Components 1.5
- Microsoft Data Access Components 2.0
- Microsoft Data Access Components 2.1
- Microsoft Data Access Components 2.5
- Microsoft Data Access Components 2.6
- Microsoft Data Access Components 2.7
This article was previously published under Q271649 SUMMARY
Microsoft does not provide any supported tool to allow tracing of OLE DB API calls. The Trace Provider tool that ships with the Microsoft Data Access Components (MDAC) version 2.5 Software Development Kit (SDK) is a beta tool and, due to design limitations, is not useful for tracing in the majority of typical OLE DB usage scenarios. The Trace Provider that ships with the MDAC 2.5 SDK can cause the traced program to crash; because of this instability, its use is not supported by Microsoft Product Support Services.
MORE INFORMATION
ODBC provides an integrated means of tracing ODBC API calls called ODBC trace. With ODBC trace, one can perform API level tracing of calls to any ODBC driver in order to debug database related problems. OLE DB does not provide a similiar feature. In order to trace OLE DB API calls, you need a debug build of the OLE DB provider as well as the source code to the provider. Microsoft does not provide the source code or debug builds of its various OLE DB providers to the public.
REFERENCESFor additional information on how to use ODBC trace, click the article number below
to view the article in the Microsoft Knowledge Base:
274551 HOWTO: Generate an ODBC Trace using ODBC Data Source Administrator
Modification Type: | Major | Last Reviewed: | 5/12/2003 |
---|
Keywords: | kbinfo KB271649 |
---|
|