| FRM-40654 after using set record property on a database block [message #690407] |
Thu, 21 August 2025 18:31  |
salviabu
Messages: 1
Registered: August 2025
|
Junior Member |
|
|
Hello,
This is a very old design.
We have a custom form have 3 blocks.
Block A, Block B, Block C.
This form is opened from another custom form by passing parameters.
Those parameters are used in where clause for Block B and Block C.
In the Post-Query of Blocks B and C, the fields for Block A are populated.
Definitely, even if no changes are made to Block A, and if we close the form, it says
"Do you want to save"
Now the client does not want this message.
We tried adding below in the Post-Query of Block B( since that one fires after post-query of Block A)
set_Record_property(:system.TRIGGER_RECORD, 'Block A', status, query_Status);
But, now we get FRM-40654 Record has been updated by another user. Re-query to see change.
What would be the best approach to handle this?
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
