What determines that flag value in a PST file is how it was created. It
can't be changed after the PST file was created. If the PST was created as
an Outlook 2003 or later PST it's Unicode enabled. If created as compatible
with earlier versions of Outlook it is not Unicode enabled.

Any items that have been synched or passed through that ANSI PST file are
already corrupted and there's nothing you can do about it.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Bert_Bert" wrote in message
...
Thanks to Oultook spy I can see more details:

on computer 1:
ost replica has this STORE_UNICODE_OK
here the characters not disappearing
on computer 2:
ost replica has this STORE_ANSI_OK and has no STORE_UNICODE_OK set
here character disappearing immediatelly

on computer 1 the character disappears after re-sync of computer 2 and
then
the data go in computer 1 damaged, which is logical

The question now is, what determines whether this flag is set.
Both computers use Outlook 2003 EN SP3.

Maybe corrupted profile? I wanted to change the valuie in Spy but it
returned error something like "VALUE_COMPUTED". But from what it is a
question.

I tried SCANOST+SCANPST. It is a kind of mystery because both computers
look
into the same Exchange directory - i.e. into the same store.

it now appears more like a client Outlook version/corruption.
By the way all PST at comp1 are ok unicode and all PST at comp2 are ANSI.

Maybe Activesync or other third party sw ?

If a store supports Unicode there is a flag set on the Store object at
PR_STORE_SUPPORT_MASK (0x340D0003). The bit that tells you if the store
supports Unicode in that PT_LONG is called STORE_UNICODE_OK. See
http://support.microsoft.com/kb/884671 for information on that flag.