XMLParseString in PB 2022
- New
- Issue
-
Nathan Mitton
- PowerBuilder
- Tuesday, 30 September 2025 05:53 AM UTC
Hi,
We have an app written in PowerBuilder 2019 that we are migrating to PB 2022 (yes I know PB 2025 is out now but the boss wants to upgrade to 2022 first, and in the interest of continuing to get paid I generally do what the boss requests).
I have noticed that some calls to XMLParseString, which succeeded in PB 2019, are now generating an 'empty string encountered' error in PB 2022. I even debug the app and get the XML that is passed in for 2019 and succeeds, and when I take that exact same XML and pass it to XMLParseString in the PB 2022 version, it fails.
Is anyone aware of the behaviour of this changing between PB 2019 and 2022? I think I can probably find a workaround for this (although if someone has a ready made workaround, I would be interested), more interested in whether it's expected to operate differently between PB versions, or if I'm missing something else.
Cheers,
Nathan
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.