1. Larry Langford
  2. PowerBuilder
  3. Tuesday, 28 December 2021 16:07 PM UTC

I'm experiencing an issue for a window with a Rich Text Edit control.
When the window containing the control is first opened we get an error:
OLE Error Error Code: 80030003
Followed by another: Error creating OLE storage
The window then opens, but the RTE isn't functional.
If we close the window and without restarting the application
open the same window, it works as expected.
It does not behave this way when running the application
from within the developer environment so it's a little challenging to debug.
We suspect it has to do with the Runtime Objects.
Can you tell me which of the RTE related objects are needed to Paste to an RTE
then save the RTE as a pdf file?

Accepted Answer
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 28 December 2021 17:37 PM UTC
  2. PowerBuilder
  3. # Permalink

Which version of the RTE control are you using?

To determine, open the Application Object, click on the "Additional Properties" button shown on the "General" tab in the Properties pane. It should appear similar to this:

These each use a unique set of DLL's. The TX Text Control (the 2nd one listed) uses an OCX (I think it is named tp4ole14.ocx), whereas the Built-in Rich Edit Control does not.

Comment
There are no comments made yet.
Larry Langford Accepted Answer Pending Moderation
  1. Tuesday, 28 December 2021 22:16 PM UTC
  2. PowerBuilder
  3. # 1

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.

Comment
  1. Armeen Mazda @Appeon
  2. Wednesday, 29 December 2021 00:46 AM UTC
Glad to hear you have a workaround.
  1. Helpful
There are no comments made yet.
Larry Langford Accepted Answer Pending Moderation
  1. Tuesday, 28 December 2021 17:48 PM UTC
  2. PowerBuilder
  3. # 2

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

Comment
  1. Mark Goldsmith
  2. Wednesday, 29 December 2021 15:21 PM UTC
Yes, just double-click in the white space between the drop-downs to bring up the various dialogues.
  1. Helpful 1
  1. Miguel Leeuwe
  2. Wednesday, 29 December 2021 21:54 PM UTC
Ha, I think it was you who told me about that option. Thanks for reminding me!
  1. Helpful
  1. Mark Goldsmith
  2. Thursday, 30 December 2021 13:28 PM UTC
YW Miguel ;)
  1. Helpful
There are no comments made yet.
Larry Langford Accepted Answer Pending Moderation
  1. Tuesday, 28 December 2021 16:34 PM UTC
  2. PowerBuilder
  3. # 3

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.

Comment
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 28 December 2021 16:26 PM UTC
  2. PowerBuilder
  3. # 4

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

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.