Hi all,
Recently i had an issue with saving new data to database via my oracle form. When i enter new records via form and press save button , occurs "FRM-40401: No changes to save" message. New records were not in database. To handle this i used "STANDARD.COMMIT" instead of using "COMMIT_FORM".
The COMMIT (COMMIT_FORM) statement analyses blocks that exist in a form. If you change a table independently from the declared blocks, then the form doesn't think that it has any changes to save. It usually leads to the "FRM-40401: No changes to save" message.
But, if you use STANDARD.COMMIT, it will bypass any checking and do exactly what you have asked - commit, now!
It is also suggested to use 'standard.commit' (NOT 'commit') in procedures that reside in a form
The COMMIT (COMMIT_FORM) statement analyses blocks that exist in a form. If you change a table independently from the declared blocks, then the form doesn't think that it has any changes to save. It usually leads to the "FRM-40401: No changes to save" message.
But, if you use STANDARD.COMMIT, it will bypass any checking and do exactly what you have asked - commit, now!
It is also suggested to use 'standard.commit' (NOT 'commit') in procedures that reside in a form
I faced the same issue while trying to save some records.STANDARD.COMMIT worked for me as well
ReplyDelete