STnefProblem
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
Contains information about a property or attribute processing problem that occurred during the encoding or decoding of a Transport Neutral Encapsulation Format (TNEF) stream.
Header file: |
Tnef.h |
typedef struct _STnefProblem
{
ULONG ulComponent;
ULONG ulAttribute;
ULONG ulPropTag;
SCODE scode;
} STnefProblem;
Members
ulComponent
The type of processing during which the problem occurred. If the problem occurred during message processing, the ulComponent member is set to zero. If the problem occurred during attachment processing, ulComponent is set equal to the corresponding attachment's PR_ATTACH_NUM (PidTagAttachNumber) value.ulAttribute
Attribute associated with the property indicated by the ulPropTag member or, when the TNEF processing problem occurs when decoding an encapsulation block, one of the following values:attMAPIProps
Message levelattAttachment
Attachment level
ulPropTag
Property tag of the property that caused the TNEF processing problem, except when the problem occurs when decoding an encapsulation block, in which case ulPropTag is set to zero.scode
Error value indicating the problem encountered during processing.
Remarks
If an STnefProblem structure is not generated during the processing of an attribute or property, the application can continue under the assumption that the processing of that attribute or property succeeded. The only exception occurs when the problem arose during decoding of an encapsulation block. In this case, the decoding of the component corresponding to the block is stopped and decoding is continued in another component.
See Also
Reference
PidTagAttachNumber Canonical Property