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.
Some bugs have been fixed but other remains. I opened two support tickets with PowerBuilder 2022 : Bug 9279 and 9303
It's still very restrictive for us...
Regards