|After a few years of investigating and building MAPI clients applications, we shifted part of our development team to the "MAPI inferno" - the service providers. This area of MAPI cannot be done with any kind of third-party custom MAPI components we know - they all have proved inapplicable here.|
(Extended MAPI in DELPHI - Service Providers)
Delphi & ADO & MAPI Together
ADO Address Book
Knowing both ADO and Extended MAPI very well
one may develop one's own design of MAPI Service Provider that would unify them.
We started off with the easiest to implement but also most commonly used Service
Provider - Address Book.
For the Outlook user all entries (contacts) that our Address Book offers are read-only, that is they cannot be edited. This is done in order to avoid editing or harming the data by chance. Of course all this does not interfere with the process of sending e-mails to the users from our Address Book.
Read more for our ADO DB Extended MAPI Address Book Provider (PDF Size: 2 MB)
The IMIMSP32 is a sample message store that uses Microsoft Office Access 2000/2003 MDB or Microsoft SQL Server 2000/2005 (incl. Express Edition) as backend store.Supported Features
Basic operations. The message store supports:
Multivalued properties are supported for all objects. The message store can be used as a default message store for a MAPI client (please call for more info)
The sample message store supports moving and copying messages and folders. These operations are delegated to MAPI support functions unless an operation occurs entirely within one message store.
The sample message store supports event notification on tables (again, courtesy of IMAPITableData).
GetNamesFromIDs and GetIDsFromNames methods of IMAPIProp.
Folder-associated information (MAPI_ASSOCIATED, DEL_ASSOCIATED flags).
Love us? Hate us? Questions or comments?
If you have any questions, concerns, compliments, or suggestions about these articles - write us
Copyright © 2013 IMIBO