-
John Raghanti
- PowerBuilder
- Wednesday, 29 October 2025 01:57 PM UTC
Hi! We are running PB 2022 R3 build 3397 CloudPro Edition.
I've been seeing an increase in tickets come into our helpdesk where our application is not doing what it's supposed to be doing and I'm looking for some guidance, please.
We don't seem to be getting PowerBuilder level errors like we used to, and things are slipping through our QA department.
One example is on the line:
ids_Problem.Retrieve(il_Patientid)
The datastore ids_Problem hasn't been created. When the executable hit this line, it just simply stopped code execution with no messages or errors given to the end user. Our application continues to run.
Another example is:
as_Code = dw_Search.Object.Code[ll_Row]
In this case, the datawindow had been modified and the column name "Code" got renamed with the table prepended, e.g. "user_table_code" (please Appeon can you stop renaming existing columns on datawindow edits, please?) and the developer (me) didn't notice the name change.
When the executable hit this line, code execution just stopped with no errors or messages again. Our application continued to run. I definitely would have expected to get an "invalid datawindow row/column specified" error here normally.
Is there something we have accidently turned off that is causing this behavior now? How do we get these types of messages/errors turned back on so that our application is at least flagged in QA before it gets to clients?
Thank you!
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.