-
Richard Hartman
- PowerBuilder
- Friday, 22 August 2025 05:54 PM UTC
Our old datawindow sources say "revision 7" and the new ones (powerbuilder 2021) say "revision 21".
I found another posting for this issue here (https://community.appeon.com/qna/q-a/datawindow-update-show-row-changed-between-retrieve-and-update) with the same symptom when the were updating from pb 12.5 to PB 2022 R3, but I don't think it was really resolved. I do not know how their pb version numbers corresponds to the "revision X" in the datawindow sources, but it seems to be a similarly long span as ours. Somehow the behavior changed from the old PB to the new ones. Specifically, I think for "updatewhere=1".
In the IDE is under "Rows/Update Properties..." you get this dialog:
The thing is, that using "updatewhere=0" does sacrifice some concurrency protections, e.g. if two people are working on the same record at the same time, the "updatewhere=1" setting would provide protection should user A change it while user B has it in the window for editing. But I can't use it if it continues to provide false change detection.
So ... I found some discussion suggesting that this error may be set off by a trigger. But I am a bit confused. The trigger does not execute until you update the record. Nothing changes before then. (Also, there specifically were NOT other people editing the same record at the same time.) What would the sequence of events (data reads/writes to/from the server and the trigger actions) be that would convince powerbuilder that the record had changed while I am updating it? I would like to have the extra concurrency protection if I can figure out how to eliminate these false change detections.
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.