Upgrading to version 2019 isn't an immediate option, but we discovered another aspect of the behavior that somewhat mitigates the issue.  We use the RTE primarily as a conduit for saving a graph object to a pdf file.  We copy to clipboard the graph image, paste into the RTE, then save the RTE as a pdf.  When we run our report distribution package containing this technique as an unattended job triggered by Windows Server 2016 scheduler, we don't see the OLE error.  It only happens when we execute interactively.  We've checked the "Start In" and execution paths, and they are consistent.  Since when running interactively the error occurs only once, then doesn't reoccur while the app in open, we're inclined to label this is a nuisance.

We have the "Built-in Rich Edit Control" option selected.  Is that the recommendation?

We are using an older version of PowerBuilder:  2017 R3 Build 1858

We found the list of objects, but there isn't a clear indication the purpose for each.

We suspect the TER25.DLL may be the key.  If we could determine why the error doesn't occur after we encounter it once after the window is opened and closed, we could maybe circumvent the initial error.

Greetings, Larry - 

It would be helpful if you told us the version, release and build #'s of the PowerBuilder version you are using, please? It would also be helpful to know which version of the RTE control your app is using.

If you are using a later version of PB, you can look in Help for the topic named "runtime files" for information about the runtime DLL's needed for the various features within PowerBuilder.

Regards, John