The information in this article applies to:
SYMPTOMSWhen you encounter this problem, you have difficulty storing the PR_ENTRYID property into a fixed length field. CAUSEThe size of an EntryID is implementation specific and not defined. Therefore, defining a fixed length field for storing a variable size EntryID, in a database for example, would be impossible. RESOLUTION
You can use the PR_SOURCE_KEY property to calculate the PR_ENTRYID on a message or folder. Because PR_SOURCE_KEY is always a 22-byte property on Exchange Server, you can define the size of a field in the database in order to store this property. The PR_SOURCE_KEY can then be used to calculate the PR_ENTRYID through the use of the EntryIDFromSourceKey API.
Sample Code
STATUSThis behavior is by design. MORE INFORMATION
The PR_SOURCE_KEY property is not valid for messages and folders in Exchange Personal Message Stores(.PST). REFERENCESFor more information on PR_SOURCE_KEY property and the EntryIDFromSourceKey API, please refer to the Microsoft Developer Network. Additional query words: MAPI PR_SOURCE_KEY PR_ENTRYID EntryID EntryIDFromSourceKey kbDSupport kbGrpMsg kbMsg kbVC600 kbMAPI
Keywords : kbMAPI kbMsg kbVC600 kbGrpMsg kbDSupport |
Last Reviewed: June 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |