Mapi-Restriction does not work on Exchange
Ok, thank you Ken.
Peter
On 4 Okt., 21:39, "Ken Slovak - [MVP - Outlook]"
wrote:
Using the Outlook object model you always get an EntryID that can be
persisted. Where you have to look out for short-term id's that are only
valid for that session is in MAPI (and Redemption). Even CDO 1.21 only
returns long-term id's.
I can't speak to the speed of ExecSQL as opposed to using a MAPI
restriction, I've only used ExecSQL in tests and in playing with things to
get the bugs squashed out of ExecSQL. I always use MAPI restrictions myself.
Dmitry can speak to the relative speed of ExecSQL better than I can.
--
Ken Slovak
[MVP - Outlook]http://www.slovaktech.com
Author: Professional Programming Outlook 2007
Reminder Manager, Extended Reminders, Attachment Optionshttp://www.slovaktech.com/products.htm
"Peter Marchert" wrote in message
ups.com...
Thanks for all answers.
I use on some procedures the ExcecSQL method but it seems to be slower
than the restriction method? The code with the restriction is called
aproximately 100 times per second (or more). I create/change
appointments by looping through contact items. And on any item I have
to check if the appointment already exists.
Seems that one question is missing or I didn`t understand all answers:
Can I use the short entryid getting from an Exchange server to
reference a contact in a future Outlook session? Or is thi only the
case by using Mapi? Ken wrote in OOM I always get the long entryid but
I`m not sure if this is on Exchange so too.
Thanks Ken and Dmirty!
Peter
|