Platform SDK: MAPI |
The PR_ATTACH_LONG_PATHNAME property contains an attachment's fully qualified long path and filename.
Header file: | MAPITAGS.H |
May be exposed by: | Attachment subobjects |
Identifier: | 0x370D |
Property type: | PT_TSTRING |
Property tag: | 0x370D001E (0x370D001F for Unicode) |
The PR_ATTACH_LONG_PATHNAME property is applicable when you use any of the PR_ATTACH_METHOD property's values that indicate attachment by reference: ATTACH_BY_REFERENCE, ATTACH_BY_REF_RESOLVE, or ATTACH_BY_REF_ONLY. Platforms that support long filenames should set both the PR_ATTACH_LONG_PATHNAME and PR_ATTACH_PATHNAME properties when sending, and should check PR_ATTACH_LONG_PATHNAME first when receiving.
The client application should set this property to a suggested long path and filename to be used if the host machine receiving a message supports long filenames. Setting PR_ATTACH_LONG_PATHNAME indicates that the attachment data is not included with the message but is available on a common file server.
Unlike the directories and filenames provided by PR_ATTACH_PATHNAME, these directories and filenames are not restricted to an eight-character directory or filename plus three-character extension. Instead, each directory or filename can be up to 256 characters long, including the name, extension, and separator period. However, the overall path is limited to 256 characters.
Clients should use a universal naming convention (UNC) in most cases when the file is shared, and should use an absolute path when the file is local and in some shared cases, such as with NetWareŽ.
MAPI works only with paths, filenames, and other strings passed to it in the ANSI character set. Client applications that use paths and filenames in an OEM character set must convert them to ANSI before calling MAPI.