Yes, it should be unique. EntryID's will change in an Exchange mailbox if
the item is moved or deleted. They don't change in a PST file. That's
transport dependent. Exchange also provides short-term and long-term
EntryID's, for a PST file you only get a long-term EntryID. So when using a
MAPI table for example you would check for both EntryID's to make sure you
get a valid result.

Signature
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm
> Hello!
>
[quoted text clipped - 15 lines]
>
> Andreas
Andreas Schachl - 09 Sep 2004 15:47 GMT
> Yes, it should be unique. EntryID's will change in an Exchange mailbox if
> the item is moved or deleted. They don't change in a PST file. That's
> transport dependent. Exchange also provides short-term and long-term
> EntryID's, for a PST file you only get a long-term EntryID. So when using a
> MAPI table for example you would check for both EntryID's to make sure you
> get a valid result.
Thanks!
Does this mean that there is no way to "track" an item from another
application using its EntryID since if it is moved or deleted I wont
find it under its EntryID?
Thanks in advance!
Ken Slovak - [MVP - Outlook] - 09 Sep 2004 16:14 GMT
Correct. I usually store the original entry id in a user defined field and
check on that so if EntryID changes my field remains the same.

Signature
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm
> > Yes, it should be unique. EntryID's will change in an Exchange mailbox if
> > the item is moved or deleted. They don't change in a PST file. That's
[quoted text clipped - 10 lines]
>
> Thanks in advance!