I always create the OLE control as it's own object and place that object on the windows. Doing that allows you to add common code to the object and there is less chance of problems like you are seeing since the OLE object would be rarely updated.

The source code of an object that is or has an OLE control will have something like this at the bottom of the exported source file:

Start of PowerBuilder Binary Data Section : Do NOT Edit
0Cuo_webbrowser.bin
2D00000a00e011cfd0e11ab1a1000000000000000000000000000000000003003e0009fffe000000060000000000000000000000010000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
1Cuo_webbrowser.bin
End of PowerBuilder Binary Data Section : No Source Expected After This Point

Somehow the binary section is getting lost. The object source and OLE bin data are stored separately in the PBL and when the IDE exports the object prior to calling the Source Control Check-In function, it appends the bin data to the source file.

Also, the RTE control built into PB 2022 is TX Text Control Version 30. You might be able to use that and no longer license it yourself.

Hi Roland.

Thank you for your reply.

I'm not sure to understand what you mean by "I always create the OLE control as it's own object..."
Could you detail your answer ?
What is the difference with creating a Standard Visual Object of the OLE type?

For the Tx Text Control, I have problems with loss of images when converting to HTML which forced me to use Te Edit OCX.

Regards.

Thierry.

Hi Thierry, did you test the TX TextControl in PB 2022 to see it really has same problems as before?  We upgraded the version of TX TextControl in PB 2022.