|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
PidTagAttachPathname Canonical Property
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 an attachment's fully-qualified path and filename.
PR_ATTACH_PATHNAME, PR_ATTACH_PATHNAME_A, PR_ATTACH_PATHNAME_W
It is recommended that attachment subobjects expose these properties. Setting them indicates that the attachment data is not included with the message but is available on a common file server. These properties are required in conjunction with any of the PR_ATTACH_METHOD (PidTagAttachMethod) flags that indicate attachment by reference: ATTACH_BY_REFERENCE, ATTACH_BY_REF_RESOLVE, or ATTACH_BY_REF_ONLY.
Each directory or filename is restricted to an eight-character name plus a three-character extension. The overall path is restricted to 256 characters. For a platform that supports long filenames, set both these properties and PR_ATTACH_LONG_PATHNAME (PidTagAttachLongPathname).
Client applications 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.
MAPI works only with paths and filenames in the ANSI character set. Clients that use paths and filenames in an OEM character set must convert them to ANSI before calling MAPI.