Home » Developer & Programmer » Forms » Form 4.5 FRM 40654 Trigger post-change problem
icon11.gif  Form 4.5 FRM 40654 Trigger post-change problem [message #157580] Fri, 03 February 2006 07:15 Go to next message
benoizette
Messages: 7
Registered: January 2006
Junior Member
My FORM has 1 BLOCK with many ITEM. Some Item have TRIGGER POST-CHANGE where some opération are realized.
an example : :name_Block.name_item := :name_Block.name_item1 + :name_Block.name_item2
the item :name_Block.name_item has the item property "Base Table Item" TRUE.
The problem is when I update an item (:name_Block.name_item1), I commit and I update an other item
then a message FRM 40654 appears. I couldn't find an issue to perform it.
Re: Form 4.5 FRM 40654 Trigger post-change problem [message #157583 is a reply to message #157580] Fri, 03 February 2006 07:39 Go to previous messageGo to next message
Maaher
Messages: 7062
Registered: December 2001
Senior Member
First some general remarks:
1. Forms 4.5 is desupported since 1803 or so, upgrade if you're on a production environment.
2. POST-CHANGE triggers are there for backward compatibility. Use WHEN-VALIDATE-ITEM instead if you can.
3. Set the "DML returning value" to TRUE in the block properties or requery after the update.

This comes from memory so I cannot guarantee that this will resolve your issue.

MHE
Re: Form 4.5 FRM 40654 Trigger post-change problem [message #157589 is a reply to message #157583] Fri, 03 February 2006 08:26 Go to previous messageGo to next message
benoizette
Messages: 7
Registered: January 2006
Junior Member
Forms do not allow to requery (EXECUTE_QUERY) into When_validate_item or Post_change Trigger. Thus "DML....." property doesn't exit into Forms 4.5 !

[Updated on: Fri, 03 February 2006 08:27]

Report message to a moderator

Re: Form 4.5 FRM 40654 Trigger post-change problem [message #157613 is a reply to message #157589] Fri, 03 February 2006 09:33 Go to previous messageGo to next message
Maaher
Messages: 7062
Registered: December 2001
Senior Member
Like I said: you are working with a medieval version of Forms. Let it go.

What I meant was:
option A: After the commit, requery. A KEY-COMMIT can help you: put the commit in there, along with the execute_query.

option B: set the block property 'DML returning value' to 'Yes'...but it's entirely possible that it's not possible in Forms 4.5. But the last time I saw Developer/2000 R1 was back in '99 Wink

MHE
Re: Form 4.5 FRM 40654 Trigger post-change problem [message #158197 is a reply to message #157613] Wed, 08 February 2006 23:51 Go to previous messageGo to next message
djmartin
Messages: 10180
Registered: March 2005
Location: Canberra ACT Australia
Senior Member
Account Moderator
Okay FRM-40654 is "Record changed by another user. Re-query to see change". It helps if the message text is posted as well as the code as I haven't memorised them all. Where do you have the ":name_Block.name_item := :name_Block.name_item1 + :name_Block.name_item2" code and where do you have the 'commit'? I suggest that you comment out ALL your commits and see if that gives you better behaviour. You don't need to have commits everywhere. Forms will tell you if you have unsaved changes.

David
Re: Form 4.5 FRM 40654 Trigger post-change problem [message #200920 is a reply to message #157589] Wed, 01 November 2006 22:29 Go to previous message
djmartin
Messages: 10180
Registered: March 2005
Location: Canberra ACT Australia
Senior Member
Account Moderator
Ben,

Did you get your problem solved?

David
Previous Topic: Urgent : Error : FRM-40654
Next Topic: window not closing
Goto Forum:
  


Current Time: Fri Dec 09 19:24:56 CST 2016

Total time taken to generate the page: 0.10985 seconds