PB 19 tracing DB error
- Issue
- Kelly Amott
- PowerBuilder
- Monday, 21 February 2022 08:44 PM UTC
I have a PowerBuilder 19 app I inherited that is producing primary key violations in the Oracle 19 DB. I have tried -
1. Step debug but the structure of the application is so convoluted that it is incredibly tedious to step through from the start.
2. Inserting multiple breakpoints where it appears obvious that the breakpoint should be but nothing triggers.
3. Profiling Trace View. This produced a pbp file that I can't read. I've tried just clicking on it and it brings up a window in PB along with an error - "Attempt to open DataWindow failed."
4. DB Trace tool. Still trying to figure this one out. Do I just replace (SQLCA) in my script with (SQLCA.DBMS = "TRACE ORA ORACLE")?
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.