This content has been marked as final. Show 4 replies
Updating a field - exchange rate in the header block - should change two fields - "price and amount" in the multi record child block - C1.There are no database triggers on any tables.
We have handled the above logic in the post -update trigger of H1. >
First, I would confirm that the logic in your Post-Update trigger of Block H1 is the cause of the error. You can do this either by deleting the trigger or by commenting out the code and only execute "NULL;". If you still get the FRM-40654 error then the Post-Update was not the problem and you still have code somewhere else that is the cause of the error.
We are also updating a summary column called "sum_amount" that belongs to H1.How are you updating this Summary Column? Is the SUM_AMOUNT column a calculated field or have you written code that updates this column? Is the SUM_AMOUNT column a database field?
It would also be extreamly helpful if you gave us your Forms version; in fact, you should always give this information! :)
If it is not Post-Update, what is the alternative apart from using the post - update trigger so that the columns price and amount are updated as soon as exchange rate is updated.Have you commented-out the Post-Update trigger yet?
Typically, I tend to use the On- or Pre- triggers (On-Update/Pre-Update). However, I think you will have the same error using either of these triggers. More importantly, I need to know the answer to my previous question:
How are you updating this Summary Column? Is the SUM_AMOUNT column a calculated field or have you written code that updates this column? Is the SUM_AMOUNT column a database field?>
We are also updating a summary column called "sum_amount" that belongs to H1.
My first reaction is that this process is the most likely cause of your FRM-40654 error, but that is just a guess.
why do you want to make direct updates to database post update. Instead, change the values in your fields "price and amount" when the user enters/updates the exchange rate. ON-UPDATE trigger will take care of updating both the tables.
or, not a preferred way to do this.. but, follow each of your update statements with FORMS_DDL('COMMIT');