MAPI_UNICODE flag in CreateMsgService , ConfigureMsgService methods

[duraisridhar]

Hi All,

I encounter following problems when I set MAPI_UNICODE to support
Unicode, although the STORE_UNICODE_OK bit was set in
PR_STORE_SUPPORT_MASK. My assumption is that MAPI_UNICODE is needed
when Unicode arguments is passed. If not so, should I work more on the
following errors.

1) The MAPI call ConfigureMsgService() returns MAPI error
"MAPI_E_UNKNOWN_FLAGS" when I set MAPI_UNICODE flag . Is using
MAPI_UNICODE flag in ConfigureMsgService() is valid?.

2) Similarly the call CreateMsgService returns MAPI error
"MAPI_E_BAD_CHARWIDTH". I just want to start the "MSUPST MS" service.
It looks fine when I call CreateMsgService without the MAPI_UNICODE
flag . I doesn't know whether the PST file created by "MSUPST MS"
service will support UNICODE, as the MAPI_UNICODE unicode falg is not
set.

Any help on this will be greately appreciated,

Awaiting your update ,

Regards,
Sridhar D,

 

[Dmitry Streblechenko]

No, it simply means that the store provider natively handles the PT_UNICODE
properties.
When you create an "MSUPST MS" service, you get a Unicode PST file, the "U"
in the service name stands for "Unicode", there is no reason to pass the
service *name* as a Unicode string - the call is not even handled by the
store provider; MAPI just looks up the appropriate service in the
mapisvc.inf file.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

 

[duraisridhar]

Hi Dmitry,
Thanks for clearing my doubts.

Regards,
Sridhar D