Important:
This is retired content. 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 content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

The MAPINAMEIDstructure is used to describe the name of a named property.

Note:
For more information on MAPI named properties, see this Microsoft Web site .

Syntax

struct {
   LPGUID 
lpguid;
   ULONG 
ulKind;
   Union {
	 LONG  lID;
	 LPWSTR lpwstrName;
   } 
Kind;
} MAPINAMEID, FAR *LPMAPINAMEID;

Members

lpguid

Pointer to a GUIDstructure that specifies which Property Set the named property belongs to. The only valid value is PS_MAPI., and cannot be NULL.

ulKind

Specifies which format to use for the property name: either numeric ( Property Tag ) or string (property tag constants as defined in the Mapitags.h header file). Its value specifies the type of object contained in the Kindunion. Valid values are as follows:

MNID_ID

The Kindmember contains the property name formatted as a numeric Property Tag . Value = 0.

MNID_STRING

The Kindmember contains the property name formatted as a Unicode character string. Value = 1.

Kind

Contains the name of the named property, as either an integer value in lID, or a Unicode character string in lpwstrName.

Remarks

Named properties are those MAPI properties within PS_MAPI property set, with Property IDs in the range 0x8000 - 0xFFFE.

The complete set of Property Tags are defined in the Mapitags.h header file.

Named properties enable clients to define custom properties in a larger name space than is available in the MAPI-defined property identifier range.

Property names cannot be used to obtain property values directly; they must first be mapped to property identifiers through the IMAPIProp::GetIDsFromNamesmethod. For particular objects such as message objects, MAPI reserves a range of property identifiers for custom properties. For these objects, clients need not use named properties, and can save the associated overhead.

Requirements

Header mapidefs.h
Windows Embedded CE Windows CE 3.0 and later
Windows Mobile Pocket PC 2002 and later, Smartphone 2002 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.