Hi to all,

After far too many hours of googling and searching MS's website, without any real result, I ask you guys for some transfer of knowledge.
I've developed a form with the MS oleRTF control and various controls to edit the RTF-text. All looks wonderful, apart from one thing. The problem has been explained by me in a former message:
Bullets in RTF Thread #663867 Message #663867

My recent research reveals that it happens in Windows 2000. Some messages/texts on googled websites mention the same problem. However, googling revealed no solutions so far. There seems to be no mention at all of the problem on the MS website.

Additional findings:
The RTF control uses Riched32.dll, which is in the Windows System/System32 map. Riched32.dll covers version 1 of the RTF protocol. In W2K Riched32.dll is merely a WRAPPER of 4K that calls Riched20.dll. (The Riched20.dll file also covers version 2 and 3 of the RTF protocol. However, those supersets will not be used by the RTF control.)
It appears that my problem is due to a flaw in Riched32.dll or Riched20.dll. But there's no mention of that at the MS site at all, that's to say, I can't find such mention.

It might be that I'm able to replace my Riched32.dll with an old version that doesn't wrap. It would be an operation after booting to DOS-only. In that case, I might be free of the bug. But I fear that the bug will still show up with users who have W2K installed.

If there's nothing that can be done about it, then I must conclude that using the RTF control is only a waste of time. It would render the control completely useless if an application (as mine) is meant for international usage!!

Reactions please!