Getting "Unresolvable external pbdom_document when linking reference at line..." error when executing the following line:
ldom_doc = CREATE PBDOM_Document
ldom_doc was declared as:
PBDOM_Document ldom_doc
In the PowerServer debugger, ldom_doc is showing as initialized as type _initsrc
I have included the latest PBDOM022.pbd in the library list, have checked to include PB DOM Runtime files in the PS Project Painter, I even moved the PBDOM.pbx file into the development directory and included it in the Files preloaded in uncompressed format list.
Code works fine in C/S, but not recognizing PBDOM_Document in PowerServer when running the deployed app. All is local on my Dev PC.
Ahhh ... I suspect that's because the PBX is 32 bit. However, after importing the PBX objects into your PBD, the PBD & its contents becomes "bit neutral". This, your imported PBD is now 64 bit compliant. Thanks for the feedback! :-)
Regards .. Chris
I suspect the issue is more likely due to the PBD not going through the process of being built from a PBL, so something done there during the build process isn't occurring for PowerServer to do its magic.
seems like the same issue I had before: https://community.appeon.com/index.php/qna/q-a/pb2022-error-calling-method-of-a-pbni-object-in-powerclient-deployment
I tried Jim's method with pbdom.pbx in an own library in an 64-bit environment. It runs in IDE, but runs endless in an Powerclient deployment, so you have to kill the app.
I imported from C:\Program Files (x86)\Appeon\PowerBuilder 22.0\IDE\
The pbdom.pbx file from \x64 can't be imported. "The file is not a valid dll or pbx file"
Deploying the same compiled app using an installer software and not the client deployment works
Still hoping for a solution for deployment via client.
Best regards
Stephan