Spurious FRM-40405 while committing changes
From: David Blethen <dblethen_at_bhe.com>
Date: Tue, 9 Nov 1999 09:32:33 -0500
Message-ID: <38282f69_2_at_news.cybertours.com>
[Quoted] I'm looking for anyone who may have seen this before. Here are the specifics:
I'm running forms 4.5 (Developer 2000) against an Oracle 7.3 database. When committing changes (do_key('commit_form');), I receive a FRM-40405 message ("No changes to apply") followed by the normal FRM-40400 message to [Quoted] indicate that the transaction is complete and the correct number of records [Quoted] have been applied and saved. The spurious 40405 comes after the POST-FORMS-COMMIT trigger would have fired and before the POST-DATABASE-COMMIT trigger would have fired (tested by posting alerts in each of these triggers to track the flow of processing as the commit takes place). The only thing that is supposed to happen between these two triggers [Quoted] is that the actual commit gets sent to the database. According to the forms [Quoted] documentation, the 40405 message shouldn't even come until later in the process flow. I tried using an ON-COMMIT trigger to overide forms default processing, but that had no impact on the message. The message still comes after the ON-COMMIT trigger has finished. Changing the SAVEPOINT mode (form [Quoted] level) from true to false had no impact. At the time the commit_form is called, only one of my blocks has a CHANGED status. All others are either NEW or QUERY status.
Date: Tue, 9 Nov 1999 09:32:33 -0500
Message-ID: <38282f69_2_at_news.cybertours.com>
[Quoted] I'm looking for anyone who may have seen this before. Here are the specifics:
I'm running forms 4.5 (Developer 2000) against an Oracle 7.3 database. When committing changes (do_key('commit_form');), I receive a FRM-40405 message ("No changes to apply") followed by the normal FRM-40400 message to [Quoted] indicate that the transaction is complete and the correct number of records [Quoted] have been applied and saved. The spurious 40405 comes after the POST-FORMS-COMMIT trigger would have fired and before the POST-DATABASE-COMMIT trigger would have fired (tested by posting alerts in each of these triggers to track the flow of processing as the commit takes place). The only thing that is supposed to happen between these two triggers [Quoted] is that the actual commit gets sent to the database. According to the forms [Quoted] documentation, the 40405 message shouldn't even come until later in the process flow. I tried using an ON-COMMIT trigger to overide forms default processing, but that had no impact on the message. The message still comes after the ON-COMMIT trigger has finished. Changing the SAVEPOINT mode (form [Quoted] level) from true to false had no impact. At the time the commit_form is called, only one of my blocks has a CHANGED status. All others are either NEW or QUERY status.
I'm sure that my users will be both confused and annoyed by this message. Has anyone seen this before? Does anyone have any ideas of what else I might look at?
Thanks,
David B.
Received on Tue Nov 09 1999 - 15:32:33 CET