Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

FRM-40654: Record updated by another user error.

1,248 views
Skip to first unread message

papal...@yahoo.com

unread,
Aug 8, 2007, 1:08:45 PM8/8/07
to
Is there a way to suppress the "FRM-40654 Record has been updated by
another user" error and automatically re-query when doing a save in
forms? I have tried trapping the error in the on-error trigger and
adding an execute_query at the end of the key-commit trigger, but so
far not successful. We are using:
Forms [32 Bit] Version 10.1.2.0.2 (Production)
Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning option
JServer Release 9.2.0.7.0 - Production
Oracle Toolkit Version 10.1.2.0.2 (Production)
PL/SQL Version 10.1.0.4.2 (Production)
Oracle Procedure Builder V10.1.2.0.2 - Production

Frank van Bortel

unread,
Aug 9, 2007, 4:27:50 AM8/9/07
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Define "not successful" - other errors? If so which?
If none - what behavior do you witness?

Did you change the message level to suppress the error?

In general, I would not want to suppress this error by
simply re-querying; I'd at least have the opportunity
to jot down what I'd entered so far.
- --
Regards,
Frank van Bortel

Top-posting is one way to shut me up...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFGutAGLw8L4IAs830RAnUSAJ0Z5Y39MY5HgTPJg2e54U3+mxigWgCfeqRp
3eQDfyAv2S6QP+jo7HwGf18=
=RsbL
-----END PGP SIGNATURE-----

F van Nimwegen

unread,
Aug 9, 2007, 5:56:53 AM8/9/07
to

What is the reason of the FRM-40654 error? When someone else has
changed the record then you should get a warning and requery, when
your commit process modifies some columns in the block at the
serverside yoy can requery after a commit or use the block properties
"DML Returning Value" and "Update Changed Columns Only".

This properties can be used from forms 6i and a 8i database to avoid a
requery when some of the columns in your block are changed by database
triggers during the commit proces.

0 new messages