1. Richard Hartman
  2. PowerBuilder
  3. 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:

 
For the section "Where Clause for Update/Delete" the source code has "updatewhere=X" where X is 0, 1, or 2.
 
The selections are:
    Key Columns (0)
    Key and Updateable Columns (1)
    Key and Modified Columns (2)
 
This problem seems to happen for "updatewhere=1" (Key and Updateable Columns).    (Again, though, in the older PB versions this seemed to work without encountering that error.)   If I use "updatewhere=0" this does not happen.   I Have not tried "updatewhere=2" yet.

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.

This is going against an MSSQL server, if this makes any difference.   The old one was going against Sybase ASE.
 
 
 
 
 
 

Responses (3)
  1. Likes
  2. Latest
  3. Oldest
Loading...

Find Questions by Tag

.EXE .NET 6.0 .NET Assembly .NET Core 3.1 .NET Core Framework .NET DataStore .NET Std Framework 32-bit 64-bit ADO.NET AEM AI Algorithm Amazon AWS Android Apache API APK App Store App Store (Apple) Appeon Workspace Appeon Xcelerator Plug-in Architecture Array ASE Asynchronous Methods Authentication AutoBuild AutoCompiler Automated Testing Automation AutoScript Azure Barcode Base64 Batch BigData BLOB Branch & Merge Browser Bug Build Button C# C# Class Importer C# Editor C# Model generator Calendar Camera Certificate Chrome Citrix Class Client Client/Server Cloud Cluster Collection COM Command Line Compiler Compression Computed Field Configuration Controls Cookies Cordova Crash Cross-Platform Crosstab CSharpAssembly CSharpObject CSS CSV Cursor Data Database Database Driver Database Painter Database Profile Database Provider DataObject DataSource DataStore DataStore (C#) DataStore (PS) DataType DataWindow DATE DATETIME DB2 Debug Debugger Debugging Deployment Design DLL DO-WHILE Dockable Docker Documentation DOUBLE Download DPI DragDrop Edge Edit Style Editor Elevate Conference Email Embedded SQL Emulator Encoding Encryption Enhancement Request Entity Entity Framework ERP Error Event Event Handler Event Handling Excel Exception Export Expression External Functions F# Field File File Access Filter Firefox Firewall Font FOR-NEXT Foreground Format Function Garbage Collection GeoLocation Git Graph HANA Hash Header HTML/5 HTTP/S HTTPClient Icon IDE Identity IIS IMAPI Import InfoMaker Inheritance Installation Integer IntelliSense Interface Internet Internet Explorer iOS IPA iPad iPhone IWA J# Java JavaScript JBoss JDBC JOIN JSON JSONGenerator JSONParser Kestrel Label Lambda Large File LDAP Library License LINQ Linux OS Load Balancing Localization Localized PBVM Log In Log Out Logging LONG LONGLONG macOS MAPI Maps MDI Memory Memory Leak Menu Merge MessageBox Messagging Method Migration MIME TYPE Mobile Model ModelStore ModelStore (C#) MSOLEDBSQL Multi Threading MVC MySQL n-Tier Namespace NativePDF NVO OAuth ODATA ODBC Office Offline OLE OLEDB Online Open Source OpenAPI OpenSSL Oracle OrcaScript Other Outlook Output Package Parameter Patch PayPal PB Classic PB Native PB.NET PBC PBD PBDOM PBG PBJVM PBL PBNI PBORCA PBVM PBX PDF Performance Permission PFC Picture Pipeline Play Store (Google) Plugin Popup Port POST PostgreSQL PowerBuilder PowerBuilder (Appeon) PowerBuilder (SAP) PowerBuilder Compiler PowerBuilder Runtime PowerClient PowerScript (PS) PowerScript IDE PowerScript Migrator PowerServer PowerServer Mobile PowerServer Toolkit PowerServer Web PowerServerLabel Print Properties Proxy Publish PULL PUSH Query Regression Release Renew Resize Response REST Retrieve RibbonBar RibbonBar Builder RibbonView Rich Text Roadmap RPC Runtime Packager SaaS Scaffolding Script SDI SDK Security Server Service Session Single Sign-on Size SMTP SMTPClient SnapDevelop SOAP Solution Sort Source Code Speech Recognition SQL SQL Anywhere SQL Server SqlBuilder SqlExecutor SQLite SqlModelMapper Storage Stored Procedure Subscription SVN Swagger Syntax TabbedBar TabbedView Tablet TabPage Target TE Control Testing Text TFS Theme TIME Timer TLS/SSL Tomcat TortoiseGit TortoiseSVN Transaction Transparency Trial Trigger TRY-CATCH TX Control Type UI ULONG UltraLite Uninstall Unit Test Unit Testing UNIX OS Update Upgrade Upload URL User Center User Object UWP Validation VARCHAR Variable Versioning Visual Studio Visual Studio Code VM Voice Warning WCF Web API Web Extensions Web Service WebBrowser WebForms WebLogic WebSphere WildFly WinAPI Window Windows OS WinForms Wizard Workgroup Workspace WPF XCODE XHTML XML Zoom

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.