Share via

afxTraceFlags 

  • Article

intafxTraceFlags;

Remarks

Used to turn on the built-in reporting features of the Microsoft Foundation Class Library.

This variable can be set under program control or while using the debugger. Each bit of afxTraceFlags selects a trace reporting option. You can turn any one of these bits on or off as desired using TRACER.EXE. There is never a need to set these flags manually.

The following is a list of the bit patterns and the resulting trace report option:

  • 0x01   Multiapplication debugging. This will prefix each TRACE output with the name of the application and affects both the explicit TRACE output of your program as well as the additional report options described below.

  • 0x02   Main message pump. Reports each message received in the main CWinApp message-handling mechanism. Lists the window handle, the message name or number, wParam, and lParam.

    The report is made after the Windows GetMessage call but before any message translation or dispatch occurs.

    Dynamic data exchange (DDE) messages will display additional data that can be used for some debugging scenarios in OLE.

    This flag displays only messages that are posted, not those that are sent.

  • 0x04   Main message dispatch. Like option 0x02 above but applies to messages dispatched in CWnd::WindowProc, and therefore handles both posted and sent messages that are about to be dispatched.

  • 0x08   WM_COMMAND dispatch. A special case used for extended WM_COMMAND/OnCommand handling to report progress of the command-routing mechanism.

    Also reports which class receives the command (when there is a matching message-map entry), and when classes do not receive a command (when there is no matching message map entry). This report is especially useful to track the flow of command messages in multiple document interface (MDI) applications.

  • 0x10   OLE tracing. Reports significant OLE notifications or requests.

    Turn this option on for an OLE client or server to track communication between the OLE DLLs and an OLE application.

  • 0x20   Database tracing. Reports warnings for both ODBC and DAO classes, plus additional information for DAO. Turn this option on if you want tracing for either the MFC ODBC classes or the MFC DAO classes. For ODBC, you get only warnings, such as type mismatches in your DFX calls. For DAO, you get information for all exceptions, including the line and function in DAO or in the MFC DAO classes where a failure occurred.

For more information, see Technical Note 7.

See Also   afxTraceEnabled, TRACE