Discussion:
"MSUPST MS" Required only for "creating" new unicode PST files ?
(too old to reply)
Mandar
2004-08-05 13:01:01 UTC
Permalink
Hi,
I have written some MAPI test code to read/add PSTs in/to a profile.
With outlook2003, MSFT supports an additional Unicode-enabled format of PST
file.
From postings on web, I thought I need to use "MSUPST MS" as the service
name while adding unicode PST to the profile. ( in call to CreateMsgService()
)
But so far my observation is that even if I add a unicode PST to the
profile by passing "MSPST MS" ( old ansi format service name ), I'm able to
read/write PST.
So is the new service name required to be specified in the call to
CreateMsgService() *only if* you are intending to *create* a new *UNICODE*
PST file ?
If answer to above question is "Yes", are there any known issues with
opening/accessing unicode PST files with the old ansi msg. service ? Or is it
that the msg. service provider ( mspst.dll ) is capable of handling both
formats by looking at the file and the new service name is required to be
given only while creating a new PST file to tell MAPI to create a unicode PST
instead of old ansi PST ?

TIA,
Mandar.
Dmitry Streblechenko (MVP)
2004-08-05 20:21:32 UTC
Permalink
mspst32.dll implements both services. It looks at the existing PST file and
fugures out its format AFAIK.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
Post by Mandar
Hi,
I have written some MAPI test code to read/add PSTs in/to a profile.
With outlook2003, MSFT supports an additional Unicode-enabled format of PST
file.
From postings on web, I thought I need to use "MSUPST MS" as the service
name while adding unicode PST to the profile. ( in call to
CreateMsgService()
Post by Mandar
)
But so far my observation is that even if I add a unicode PST to the
profile by passing "MSPST MS" ( old ansi format service name ), I'm able to
read/write PST.
So is the new service name required to be specified in the call to
CreateMsgService() *only if* you are intending to *create* a new *UNICODE*
PST file ?
If answer to above question is "Yes", are there any known issues with
opening/accessing unicode PST files with the old ansi msg. service ? Or is it
that the msg. service provider ( mspst.dll ) is capable of handling both
formats by looking at the file and the new service name is required to be
given only while creating a new PST file to tell MAPI to create a unicode PST
instead of old ansi PST ?
TIA,
Mandar.
Mandar
2004-08-06 05:53:01 UTC
Permalink
Ok. thanks.
Post by Dmitry Streblechenko (MVP)
mspst32.dll implements both services. It looks at the existing PST file and
fugures out its format AFAIK.
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
Post by Mandar
Hi,
I have written some MAPI test code to read/add PSTs in/to a profile.
With outlook2003, MSFT supports an additional Unicode-enabled format of
PST
Post by Mandar
file.
From postings on web, I thought I need to use "MSUPST MS" as the
service
Post by Mandar
name while adding unicode PST to the profile. ( in call to
CreateMsgService()
Post by Mandar
)
But so far my observation is that even if I add a unicode PST to the
profile by passing "MSPST MS" ( old ansi format service name ), I'm able
to
Post by Mandar
read/write PST.
So is the new service name required to be specified in the call to
CreateMsgService() *only if* you are intending to *create* a new *UNICODE*
PST file ?
If answer to above question is "Yes", are there any known issues with
opening/accessing unicode PST files with the old ansi msg. service ? Or is
it
Post by Mandar
that the msg. service provider ( mspst.dll ) is capable of handling both
formats by looking at the file and the new service name is required to be
given only while creating a new PST file to tell MAPI to create a unicode
PST
Post by Mandar
instead of old ansi PST ?
TIA,
Mandar.
Loading...