FRM-40654 problems but only against one database (forms6i)

Question

Hi,
I have one very basic form. The query data source of the block is a view. The DML data target is a table. The locking mode is set to automatic. Against our development database this form runs without any problem. We can query and update records as expected. Against production we can query the records but the moment we change a field we get a FRM-40654 error. Both production and development database are the same version (8.1.6.3)
Can anybody give me some hints where I could look to find the cause of this problem.
I found note 1003629.6 on metalink. It describes some issues you can have when you work with a view as data source and a table as target but the workarounds cannot be used by me and I don't see why it would work against dev in this case.
To me it looks like we should rather change something on database level...?
Best Regards,
Kris

Answer 1

I would double-check that everything is the same. Is it possible one of the databases has a public synonym so you aren't really looking at the same view or table?
If you cannot find the problem, try eliminating all the non-essential columns from your block first. If the problem goes away, re-add them one-by-one. All you need to do to remove and then add is change the Database Item property from Yes to No.
If that does not help you find the problem, then try to emulate in SQL Plus the select and lock that Forms does: First select the data from the view into some local variables. Then to emulate what the on-lock trigger (which issues the 40654 error) does: Select the same columns using the rowid (or maybe primary key columns in your case) from the table you are updating, and then find which column has a different value from the values stored by the select from the view. One of these columns has a different value, and that is triggering the error message.