French Unicode characters disappearing from user defined fields

[Bert_Bert]

Outlook 2003, EN:

Hi,
I have created customized form flexible dictionary for learning foreign
laguages and flexible maintaining of vocabulary.

However, I have problem that Czech unicode characters are kept as entered,
for example: Ä› Å¡ Ä Å™ ž ý á í
these are ok

On the other hand French ones as: û è à â ç
these disappear after I save and reopen the Item.

This is really annoing, can someone please provide me at least some clue
what mechanism can be behind to be able to better understand how to
troubleshoot this?

In my computer I use Czech Regional settings (at Windows XP SP2 EN version)
as default.

any help appreciated

 

[Pat Willener]

It may be an encoding thing, i.e. ISO-8859-2 vs. Unicode-UTF8. I don't
know how to use encoding on forms, so I can't help you with the details.

 

[Bert_Bert]

I found the solution - in case someone has similar problem i future.

I installed Outlook Spy and checked iMapiFolder PR_STORE_SUPPORT_MASK and in
the OST store I found STORE_ANSI_OK and not STORE_UNICODE_OK as expected.

On the other computer looking into the same Exchange mailbox I could see
STORE_UNICODE_OK flag and here the chars did not disappear.

Therefor I tried to logon to a new Windows profile and after syncing
Unicoide flas has been there !

So I knew problem was somewhere in a profile, since in the bad one I could
not setup any new Mail profile - was not able to check with Exchange username.

I did not do any other investigation because it would cost me lots of time
and I just renamed Windows profile not to have re-install windows and set up
fresh mail account that has Unicode support OK.

Now, french characters not disapperaring and all work fine !!!

one little problem though, CDO 1.21 does not handle unicode or I do
something wron, but it is rather a question to programming part

If you would any hint, just for fun, I have still the bad profile, what
could cause the corrution.... It must be something in the whole Windows
profile but not in the all Windows....

It is strange from what actually the flag is calculated.

 

[Ken Slovak - [MVP - Outlook]]

CDO 1.21 does handle Unicode, you just have to use the "W" equivalents of
the ANSI property tags you're probably using.

For example, the ANSI tag for Body is CdoPR_BODY = &H1000001E. The "W" tag
would be CdoPR_BODY_W = &H1000001F.

It's the same when using Extended MAPI, if you have the STORE_UNICODE_OK
flag set on the Store then you use the "W" property tags to get back the
Unicode property values, you use the "normal" property tags to get back the
ANSI property values (for PT_STRING8 properties).

 

[Bert_Bert]

wow! this is extremely interesting for me in my CDO.hlp there is not a word
about unicode
however I am getting property ID programatically in the following way:
Set f=message1.Fields
Set myField = f.Item(txtPropName)
lngPropTag = myField.ID

as I observed from behaviour, the field I get is not the Unicode one. I am
afraid if possible to get _w version programatically for user defined fields
??

 

[Bert_Bert]

I tested this and it seems CDO really has no support for unicode.
However if I use Outlook object model for item of the same ID, it returns
the unicode, but I cannot use it because it is terribly slow and buggy
(memory leaks).
So if CDO could be used with unicode this would help me a lot.

 

[Brian Tillman]

I tested this and it seems CDO really has no support for unicode.
However if I use Outlook object model for item of the same ID, it
returns the unicode, but I cannot use it because it is terribly slow
and buggy (memory leaks).
So if CDO could be used with unicode this would help me a lot.

Perhaps the programmers in microsoft.public.outlook.program_vba or
..program_addins can suggest something.

 

[Ken Slovak - [MVP - Outlook]]

CDO 1.21 does support Unicode using those "W" property tags, but your store
has to support Unicode also. There's no special support for Unicode in CDO
but there isn't in the Outlook object model or Extended MAPI either, other
than using the correct property tags.