1. Giuseppe moglia
  2. PowerBuilder
  3. Thursday, 2 December 2021 16:00 PM UTC

Hi Guys

I've a workspace containing 3 targets connected to svn

In all these targets there is a library with a window containing an olecustomcontrol

If I run this window in one of these target it works like a charm, if I try to call it from another target the application crashes with a log and a dump file I share with you

Any hints?

Thanks in advance

 

Attachments (1)
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Monday, 6 December 2021 09:18 AM UTC
  2. PowerBuilder
  3. # 1

Hi Giuseppe,

Thanks for your feedback on this issue. WebBrowser does have Bug in this aspect. You can see https://www.appeon.com/standardsupport/track/view?id=7329 for details.
Our engineers are analyzing the issue but as it involves third-parties, we still need some time to figure it out.

Regards,
Ken

Comment
There are no comments made yet.
Giuseppe moglia Accepted Answer Pending Moderation
  1. Friday, 3 December 2021 16:24 PM UTC
  2. PowerBuilder
  3. # 2

Hi Guys I find out the cause of the crash (With support of my colleague of course) !!!!

 

It seems there is an incompatibility between libraries from pbcef and OLE CRVIEWER 11.5

In attachment an example, is there a way to fix it?

I tried with PB2019 R3 and PB 2021 with no chance

I've attached a PB code to replicate the case:

I've 2 window one containing a webbrowser, the other containing the oleobject of CRVIEWER

If you open the w_webbrowser and after that the w_crviewer the app crashes

If you open the w_crviewer and after that the w_webbrowser tha app does not crash but after that if you call a property of the ole or simply close the w_crviewer the app crashes

If you create a window with both crviewer and webbrowser when you open it it crashes

Here the link to download the installer of CRVIEWER

https://www.dropbox.com/s/c6sspf84odgyp9n/CRXI_Installer.msi?dl=0

thanks for the support

Attachments (1)
Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 2 December 2021 18:58 PM UTC
  2. PowerBuilder
  3. # 3

Hi Giuseppe; 

   If you edit the source code from the IDE's System Tree, you will not see the mapping. If you export the source code though, you will see it. The PB IDE source editor masks the fact that the mapping is in the source code of the resident object where the OLE/OCX is declared. For example:

HTH

Regards ... Chris

Comment
There are no comments made yet.
Giuseppe moglia Accepted Answer Pending Moderation
  1. Thursday, 2 December 2021 17:31 PM UTC
  2. PowerBuilder
  3. # 4

Thank you 

Chris

one more question

When I set up an olecustomcontrol in a window in its properties I can see its name:

 

but where is stored this info?

If I get the source of the window this name is not present at all, is it into the pbl?

 

Thanks

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 2 December 2021 17:05 PM UTC
  2. PowerBuilder
  3. # 5

Hi Giuseppe;

   My guess is that your secondary Target is either a) missing a PBL that requires a related dynamic component at execution time; b) your secondary target is pointing to an outdated PBL that is the same name as in the 1st target's list but a different outdated instance or c) you have a duplicate object that gets picked up because the secondary Targets library list order is different.

Regards ... Chris

Comment
  1. Giuseppe moglia
  2. Thursday, 2 December 2021 20:22 PM UTC
Hi Chris

I've debugged the application and the error happens in the create of the window at this instruction:



this.ole_crw=create ole_crw



How can it depends on library list?



Thanks
  1. Helpful
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.