Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved AutoBuild problem with deploy PBDOM library

  1. Advice
0
Votes
Undo
  1. Paweł Kasperek
    Paweł Kasperek
  2. PowerBuilder
  3. Wednesday, 7 June 2023 15:07 PM UTC

Hi,

I have got a problem with deploying the PBDOM wrapper library via PBAutoBuild. I use PowerBuilder 2022. I created a wrapper library of PBDOM extensions the same as it's written in the documentation (https://docs.appeon.com/pb2022/application_techniques/Adding_pbdom125.html). The wrapper PBL library is compiled to PBD library from traditional deployment from PowerBuilder IDE. If I use PBAUtoBuild the PBD library isn't created. I've followed the build warning:

[Warning] Object: pbdom_document
[Warning] pbdom_document Class Declaration
[Warning] (0014): Error C0123: Function getownerdocumentobject differs from ancestor only by return type.

during build from PBAutoBuild, but it's not from PowerBuilder IDE.  Where is the error ? 

Regards.

Pawel

  1. PBDOM
  2. AutoBuild
Datawindow Group question
Barcode Printer (SATO CL4NX Plus) USB001 Port
Accepted Answer
Paweł Kasperek
Paweł Kasperek Accepted Answer Pending Moderation
  1. Thursday, 8 June 2023 10:52 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi,

Thank you for helping. I resolved my problem in two ways:

  • I used the proposed solution by Chris Pollach. It's work.
  • I changed the name of my PbDom wrapper library. I removed PbDom substring from its name. It's work. The PbAutoBuild makes PBD library with PBDom objects. So, the proposed solution from official documentation also works.

Regards,

Pawel

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 8 June 2023 12:11 PM UTC
That's awesome news Pawel ... Super glad that you resolved this issue! :-)
  1. Helpful
There are no comments made yet.
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 7 June 2023 18:26 PM UTC
  2. PowerBuilder
  3. # 1

HI Pawel;

  FWIW: I would suggest ...

  1. Remove all the PBDOM objects from your current App's libraries.
  2. Do not use the PBNI approach as per the PB documentation.
  3. Copy the PBDOM220.pbd from the PB 2022 installation area to your App's workspace folder
  4. Add the PBDOM220.pbd  to your App's Target library list
  5. Now compile & deploy as usual.

   Here is an example of my App configured with PBDOM as a PBD (no PBNI used) and deploy-able in either M-Code, P-Code, PowerClient or PowerServer App EXE's and in either in 32 bit or 64 bit architecture.  All works perfectly.  :-)

HTH

Regards ... Chris

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.
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.